Open DanielGoehler opened 4 years ago
Any idea how to remove this code? I've commented out the flowfield and calctype to make to make it a regular field and it still throws this time out error visible only in the event viewer
@BazookaMusic it would really helpful if this warning (error) gets added, since this would avoid Runtime Errors, that potentially prevent a user opening some page where such FlowFields are added. This is still not controlled on compile time with latest AL Langauge Extension: v10.2.719883
@pri-kise atoader left Microsoft a long time ago.
Maybe MS should document first, in which cases flowfields on flowfields are allowed and in which cases they aren't. I'm using lookup flowfields on lookup flowfields with success for many years so it shouldn't be a general analysis rule.
Good point, at least (most?) lookup
within lookup
are OK.
MS should clearly document which are meant to work, which are not and why, and the latter subset should be compile-time errors - not run-time ones.
Description It would be nice, if the compiler would catch FlowFields on FlowFields.
Reason for the rule The compiler has all information to prevent that runtime error. Sometime you get an runtime error message
and the Page will be closed.
And sometimes the Web Client crashes. Event Log when this happens:
Bad code sample
Versions: