-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SubPageLink Enums #14372
Comments
Pragma is a workaround. When compiling the baseapp we also have the same warning. Probably there will be a large scale notification when these will really become errors. |
Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one. |
Out of interest, what was the fix? Are warnings relaxed for Enum vs Option links, or was just the one page in the OP changed to Enum? I guess not the latter, since that table has to link to various different sets of possible document types. |
Looks like a lot of #pragma warning disable / #pragma warning restore were added around "Source Subtype" = FIELD(...). I guess that means this won't turn into an error anytime soon. |
1. Describe the bug
Using the SubPageLink on a Factbox with a field that has a filter from an enum to an option you get warning AL0603, and eventually become an error. So for example mine is using Sales Header Document Type and going to Reservation Entry Source Subtype.
2. To Reproduce
Use a Subpage Link that has a filter that goes from Enum to Option.
3. Expected behavior
Is this something we have to use Pragma for or is this something that will become an error? since this is a base application table, I cannot change the option to an enum.
4. Actual behavior
You get a warning
5. Versions:
The text was updated successfully, but these errors were encountered: