My biggest frustration with any fields that are not Table Fields or Flowfields is the inability to sort on filter on them when you are in a list view. Microsoft needs to fix this... thanks for the great video Erik. I love the label field without caption. Great hack.
This is similar to coding in onaftergetrecord trigger of the page. I can see that coding via page expressions is simpler. But is it faster than coding it in onaftergetrecord?
In this exaple you are passing Rec,which is from your SourceTable Record. If I have another source table and want to pass it to my field expression should I declare it as var or how?
Example: I wanna extend the pages Posted Whse. Shipment Header List and Card with 4 new fields using a procedure. Should I place the same 4 functions into both pages or should i put them into a tableextension or a Codeunit? My questions/thougts: 1.) Placing the same functions into multiple places is not optimal for ex. if I have to modify them. 2.) If I only place a function into a tableextension is it then as "bad" as adding new fields in terms of performance? 3.) With a Codeunit I have to use a global variable.
In code, by controlling the Visible= property of the field. without code, with this appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.efoqus-5058796%7CAID.security%7CPAPPID.7c4b9095-058f-4464-a4d0-104cc305e68c?tab=Overview
My biggest frustration with any fields that are not Table Fields or Flowfields is the inability to sort on filter on them when you are in a list view. Microsoft needs to fix this... thanks for the great video Erik. I love the label field without caption. Great hack.
cool trick about Labels as clickable actions! :)
Great video, once again:-) Maybe you could have mentioned CaptionClass as a really nice way of getting the caption from a field or the table itself.
Great class!
quick question: what do you press to auto fix code indentation?
It's the Document Formatter. You can force it from the command palet or have it auto-format when you save the file.
Thanks for the video! Expression without Rec will be read-only?
No, expression that is more than just an identifier, will be read-only.
This is similar to coding in onaftergetrecord trigger of the page. I can see that coding via page expressions is simpler. But is it faster than coding it in onaftergetrecord?
In this exaple you are passing Rec,which is from your SourceTable Record. If I have another source table and want to pass it to my field expression should I declare it as var or how?
But a page can only have one SourceTable, not sure what you're asking about?
Example: I wanna extend the pages Posted Whse. Shipment Header List and Card with 4 new fields using a procedure.
Should I place the same 4 functions into both pages or should i put them into a tableextension or a Codeunit?
My questions/thougts:
1.) Placing the same functions into multiple places is not optimal for ex. if I have to modify them.
2.) If I only place a function into a tableextension is it then as "bad" as adding new fields in terms of performance?
3.) With a Codeunit I have to use a global variable.
I would put them in a tableextension. The performance issue is only for actual fields, not code.
is ApplicationArea value case-sensitive or not?
not, otherwise I would be in big trouble all the time :)
How about filters on expression fields? no filter on page :(
Example?
if we add a field on page, and we wan't only 1 user to see that, look into this how it is done?
In code, by controlling the Visible= property of the field. without code, with this appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.efoqus-5058796%7CAID.security%7CPAPPID.7c4b9095-058f-4464-a4d0-104cc305e68c?tab=Overview
I have one more question
I want to write code for print multiple invoices at one requestpage
You can filter on multiple invoices on the report?
Let suppose I'm on Sales Invoice listpage and I'm selecting multiple invoices and now i want to print them, how i can do that