Hi Team, I am working on cloud version of Manager.io and appreciate a lots of developments had been made with time!
Earlier, I was able to extract Custom Reports with Custom Fields in past organizations. However, I have created a new business entity for recent organization and unable to extract Custom Field data on Custom Reports.
Can you please assist me here so I can extract the data in Custom Report and please also help me to understand the difference between Custom Fields and CustomFields2.
Welcome back @Rajwani,
Custom Fields are the previous implementation, aka Classic Custom Fields found under Settings > Obsolete Features.
CustomFields2 are the new implementation and they are not compatible with Custom Reports.
For tab specific reports, you can now do so using Advanced Queries on tab views, relates lines views.
For GL based reports, you can use Advanced Queries on Summary > Transactions, howeve, here you cannot see any Custom Fields, unfortunately.
Hi Ealfardan, thank you its pleasure to reconnect!
Appreciate your prompt response with such guidance and clarity. I might have to revisit for custom fields parameters, I had set-up a lot of information while deploying it.
Do we expect that the feature will be enabled in “Custom Reports”, like it was for “Classic Custom Field”.
Tab & GL report can suffice the utility to an extend in extracting data and validating the details limited to it, however, “Custom Report” is dynamic and pull information from multiple sources & give a wholistic picture which is easy and quick to absorb all things at once. Is there any specific reason for not having this feature for “CustomFields2”.
The reason being that Manager is moving away from Custom Reports in favor of Advanced Queries.
I agree though that upgrading to CustomFields2 places the user in an uncomfortable place especially if the user relied on Custom Reports for cross tab data.
I vaguely recall the developer hinting at exposing Custom Fields to Transactions tab but I don’t think that that would be enough since this still ignores tab specific fields such as Due Date for example.
I would really like to place this in ideas, but I’m not sure what @lubos has in mind here
How does @lubos expect us to pull data from General Ledger Transactions linked/filtered with new custom fields since old custom reports don’t link to new custom fields and advanced queries don’t query from General Ledger Transactions?
