You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Report Extension Object: Error AL0680: Cannot use addBefore or addAfter on a top-level data item. The anchor Prod. Order Line is a top level data item
#12940
I wrote a report extension object. It worked fine in our Sandbox environment and AL code analyzers did not complain.
We are running BC SaaS, v18.1.24822.24906.
After I uploaded it to our Production environment (6/18/2021), I received an email from Microsoft (6/19/2021) stating:
Your extension needs updating....
Validation results:
Environment: "Production"
Application Version: 18.3.27014.0
Errors:
Error AL0680: Cannot use addBefore or addAfter on a top-level data item. The anchor Prod. Order Line is a top level data item.
....
Review the breaking changes and how to resolve them.
Use addfirst and addlast for placing your actions on Business Central pages. This eliminates breaking your app due to Business Central core changes.
In the report extension object, I changed addafter to addlast. The report extension seemed to function the same. I then uploaded the new version to Production.
After doing so, I checked Deployment Status, which showed as FAILED (although the extension works as expected).
Yet for the original extension, it had shown as Completed, but then received the Microsoft email.
To further assess the FAILED status, I accessed Environments -> Manage Apps, but it apparently only shows apps from AppSource.
As well, I looked at Telemetry in Admin, across the time from the extension being installed, but it is not pulling back any Failure messages.
I also searched through Current release plans and dynamics365-2021-release-wave-1-plan.pdf, which links back to Report Extension Object. But did not find any additional information.
So, I am not certain what is causing the app to FAIL now, why it showed as Completed on 6/18/2021, but then received the Microsoft email.
Has anyone encountered the same error, or have additional information that would explain the error?
As well, can anyone explain why the Deployment Status showed as Complete with the original extension and then showed as FAILED with the updated version, with only the change from addafter to addlast?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I wrote a report extension object. It worked fine in our Sandbox environment and AL code analyzers did not complain.
We are running BC SaaS, v18.1.24822.24906.
After I uploaded it to our Production environment (6/18/2021), I received an email from Microsoft (6/19/2021) stating:
The only semi-related reference I could find was In Technical Validation.
In the report extension object, I changed addafter to addlast. The report extension seemed to function the same. I then uploaded the new version to Production.
I also searched through Current release plans and dynamics365-2021-release-wave-1-plan.pdf, which links back to Report Extension Object. But did not find any additional information.
So, I am not certain what is causing the app to FAIL now, why it showed as Completed on 6/18/2021, but then received the Microsoft email.
Has anyone encountered the same error, or have additional information that would explain the error?
As well, can anyone explain why the Deployment Status showed as Complete with the original extension and then showed as FAILED with the updated version, with only the change from addafter to addlast?
Beta Was this translation helpful? Give feedback.
All reactions