Two ways to add custom field – one method not saving
22 December, 2013
When adding a custom f(x) field to report, I've found the following method the easiest.
I go into the report output, and right click on a particular column, and choose the custom function I need for my field.
It populates instantly.
However, when I leave report, and come back in, the column is gone.
If I use the alternative method, by adding the custom f(x) field in the data section of creating report, the custom field stays.
However, the report is now taking a long time to generate, 5-10 seconds. Even though it is the exact same function.
I get a feeling that it is calculating the custom field based on the entire dataset (i.e. 5 million member records), rather than just the output of the report (which is only 52 records, because I have set a filter that only shows a member count for the most recent 52 weeks)
Hi Samuel,
looks like you've found a bug! The Advanced Function column that you add by the Add f(x) method on the Report Format screen should definitely be there the next time you open the report. So I've raised a defect (support task 152017) and will get the developers onto it in the new year.
As to the report running slower when you add the Advanced Function in the Report Builder screen 1 rather than on the final Report Format screen, that must somehow be caused by something else because both methods of adding the function end up calling the same block of code. In other words the only difference is how you add the function but once it's there then it's the same code. As to going through the entire dataset, this is not possible as Yellowfin applies the Advanced Function after the resultset has been returned. You can verify this by observing the Report SQL for a report that has an Advanced Function, you will see that there is nothing in the actual SQL that does the calculations, i.e. the calculations are done in the java coding on the returned result set.
regards,
Dave
looks like you've found a bug! The Advanced Function column that you add by the Add f(x) method on the Report Format screen should definitely be there the next time you open the report. So I've raised a defect (support task 152017) and will get the developers onto it in the new year.
As to the report running slower when you add the Advanced Function in the Report Builder screen 1 rather than on the final Report Format screen, that must somehow be caused by something else because both methods of adding the function end up calling the same block of code. In other words the only difference is how you add the function but once it's there then it's the same code. As to going through the entire dataset, this is not possible as Yellowfin applies the Advanced Function after the resultset has been returned. You can verify this by observing the Report SQL for a report that has an Advanced Function, you will see that there is nothing in the actual SQL that does the calculations, i.e. the calculations are done in the java coding on the returned result set.
regards,
Dave
Glad to help.
Having a look through YF 7.0 there seems to be less distinction between the previous two methods of adding an Advanced Function. In any case, it works great.
Thanks!
Having a look through YF 7.0 there seems to be less distinction between the previous two methods of adding an Advanced Function. In any case, it works great.
Thanks!