|Tony||# Posted on March 1, 2018 at 9:29 am|
Whilst hiring a developer will likely still be necessary, I have a couple of questions on the above as (without knowing all of the details) some of what you are trying to do appears to be the wrong approach.
The information that you are adding to custom fields could be pulled directly from EE on the front end output rather than added to a custom field to then be pulled on the page.
I don’t know all of the details for what you are trying to do, but it sounds like a long winded method to pull the info you need and display it. For example for ‘count of dates from the event’ you could count all of the datetimes on the event and just output that directly, however its not clear if you mean all active datetimes, or upcoming datetimes, or just all datetimes regardless of status which changes things a fair bit but the point being you should just be able to pull that data directly rather than using custom fields.
Could you not just add those to the registrations CSV report we currently have?
Not really, the registration pulls the registrations and then the details liked to those registration (like the event) so it can’t really pretend theres registrations and look over those pretend registrations to pull the events.
With the amount of work involved to try and get something like that to work it would be better focusing that time on creating a new report imo.