Hey Erik, thanks for the nice educational video. Visual Basic was very nice introduction to programming, but when I revise old code, these forms look so ancient. Keep with the great work, all the best!
EH (or anyone else), I'm getting a "The supplied field number '45' cannot be found in the 'Job' table" when clicking on the Job Number FlowField link, when I specify "DrillDownPageId = 88". Any advice appreciated 🙏
It's not "exactly" the same formula but ex: to show several fields from one Item record like Description, Description 2, Gross Weight, Net Weight, Unit Volume, Durability etc...
The business value is, I guess, visible when there is a lot of entries, and the field is only needed for one particular case. It will save you space, and maybe will improve response time from the SQL @@ant1d0te
I still think it's a weird... politeness? courtesy?... to older developers that these pages are still called * Subform, given that in the AL development environment there is no schema update when renaming pages. It's probably more a compatibility reason it's not renamed, but none the less MS could just hit a big red button and say "Nah it's * Subpage now, we're big enough not to care about your broken dependency"
@@Hougaard Found it and you steered right around the issue of getting actual AI generation of content which I have the most interest in and find most challenging and hoped to pick up some tips on :)
@@Hougaard Hi Erik, "I'm comparing them with The Virtual fields. With that being said, I had these issues: You can’t do nothing (*, +, /) with the returning value; you cannot make the field a normal field again, it needs to stay as FieldClass = FlowField; it cannot be used to filter a record (at least I couldn’t find a way to do it); you need to keep them in mind to recalculate them when working with records; you cannot use variables to filter them. (My apologies if these are just a lack of knowledge on my part)."
Hey Erik, thanks for the nice educational video. Visual Basic was very nice introduction to programming, but when I revise old code, these forms look so ancient. Keep with the great work, all the best!
So how can editable flowfields be used nowadays? It was, or are maybe still used on Budget entries but are there other use cases for them?
Impeccable timing EH! Was about to look into putting Job Numbers on the Sales Invoice List page and this was almost a copy and paste solution 🤘
EH (or anyone else), I'm getting a "The supplied field number '45' cannot be found in the 'Job' table" when clicking on the Job Number FlowField link, when I specify "DrillDownPageId = 88". Any advice appreciated 🙏
This looks simple and very effective.
Cannot figure out what would be the benefit to have several flowfields in one table having the same formula?
To get more than one field.
@@Hougaardstill do not see any meaningful business value in this, do you hve an example by chance?
It's not "exactly" the same formula but ex: to show several fields from one Item record like Description, Description 2, Gross Weight, Net Weight, Unit Volume, Durability etc...
The business value is, I guess, visible when there is a lot of entries, and the field is only needed for one particular case. It will save you space, and maybe will improve response time from the SQL @@ant1d0te
I still think it's a weird... politeness? courtesy?... to older developers that these pages are still called * Subform, given that in the AL development environment there is no schema update when renaming pages. It's probably more a compatibility reason it's not renamed, but none the less MS could just hit a big red button and say "Nah it's * Subpage now, we're big enough not to care about your broken dependency"
Hi Erik
think you have some great videos, could you in near future look at the new Copilot prompt type?
There's already a video on that :)
@@Hougaard missed that will find it right away 😊
@@Hougaard Found it and you steered right around the issue of getting actual AI generation of content which I have the most interest in and find most challenging and hoped to pick up some tips on :)
I give up on FlowFields, too many issues.
What issues?
@@Hougaard Hi Erik, "I'm comparing them with The Virtual fields. With that being said, I had these issues: You can’t do nothing (*, +, /) with the returning value; you cannot make the field a normal field again, it needs to stay as FieldClass = FlowField; it cannot be used to filter a record (at least I couldn’t find a way to do it); you need to keep them in mind to recalculate them when working with records; you cannot use variables to filter them. (My apologies if these are just a lack of knowledge on my part)."