Al: Using SystemId in RunPageLink causes the client to crash

[ajkauffmann]

Describe the bug
When you use the field SystemId in a RunPageLink the client crashes with no information in the telemetry.

To Reproduce
Steps and to reproduce the behavior:
Create an action with
RunObject = Page
RunPageLink = RowId = field(SystemId);

to open a page with related records. The client will crash when you click the action.
It can be solved by writing code in the OnAction trigger to apply the filter.

Expected behavior
Either SystemId is not supported in a PageLink and then compiler should warn about it, or the runtime should just create the correct filter automatically (preferred).

Screenshots
If applicable, add screenshots to help explain your problem.

5. Versions:

• AL Language: 4.0.191880
  
• Business Central: Platform 15.0.37725.0 + Application 15.0.36560.0

[eknraw]

This also crashes the client when used in a page part subpagelink.

[tfbtrading]

Had the same issue when experimenting with linking the Documents Attachment Factbox using SystemID. Had thought perhaps we were moving to that pattern - but apparently not.

[scm6iwa]

Any news on getting this fixed as I'm going development using the systemid and linking to a factbox via SubPageLink and the client keeps crashing

[acjdekorte]

In issue #5696 it is mentioned that Microsoft is aware of the issue, but ETA when they will solve this.

[kevindstanley1988]

Hello, any status on this. This bug eliminates many of the positives that system id brings.

[kevindstanley1988]

Verified not working with version 16.4 using this project. https://dev.azure.com/wolcottgroupllc/_git/TestSubPageLink

This is a very simple example. I have a table with fields TableID and "Related To System Id". A generic list part with these 2 fields. On the Item card I added the list part with this subpagelink.

SubPageLink = TableId = Const(27), "Related To System Id" = field(SystemId);

We have been waiting for this feature to work since systemId got introduced. It makes table relations far more complex than needed by not allowing for this.

cross post from issue #5696

[tfbtrading]

This is related to in general the lack of ability to use systemid to relate and navigate between records. Using GUID for navigation between relationships is in general best practice now – the more that we see a gap between how we do this via API’s and in AL – the more challenging it will be over time.

From: kevindstanley1988 [e-mail]
Sent: Thursday, 3 September 2020 11:09 PM
To: microsoft/AL [e-mail]
Cc: Russell Kallman [e-mail]; Comment [e-mail]
Subject: Re: [microsoft/AL] Using SystemId in RunPageLink causes the client to crash (#5423)

Verified not working with version 16.4 using this project. https://dev.azure.com/wolcottgroupllc/_git/TestSubPageLink

This is a very simple example. I have a table with fields TableID and "Related To System Id". A generic list part with these 2 fields. On the Item card I added the list part with this subpagelink.

SubPageLink = TableId = Const(27), "Related To System Id" = field(SystemId);

We have been waiting for this feature to work since systemId got introduced. It makes table relations far more complex than needed by not allowing for this.

cross post from issue #5696https://github.com/microsoft/AL/issues/5696

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AL/issues/5423#issuecomment-686477578, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKFAGXUBRFONXGL44UM3S2DSD6IM7ANCNFSM4JKDK5KQ.