Debugging the Base app showing "No content available" message for some objects

[MarjanChabukovski]

Please include the following with each issue:

1. Describe the bug
debugging the base Business Central application, I noticed that the contents of various objects, eg report 7323 in Create Invt Put-away/Pick/Mvmt, are hidden. While stepping into the object instead of showing the code, it opens a file named Mvmt.dal which displays "No content available" message.

I'm trying to create an inventory pick from a PO. I can see the code for page 50 and table 38 but when it gets to the report it seems like it's not allowed to be read.

Lots of other people experienced the same issue. See the comments from April this year on this community link: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/readiness/readiness-ready-to-go#developing-for-business-central-in-general

2. To Reproduce

set a breakpoint on action("Create Inventor&y Put-away/Pick") on Page 50 and breakpoints in report 7323 and try to create a pick

1. Go to '...'

AL code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally.

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.

3. Expected behavior

expecting to be able to view all code from report 7323

4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring

5. Versions:

• AL Language: 11.0.787898
• Visual Studio Code: Version: 1.77.3 (user setup)
• Business Central: 21.5.53619.53813
• List of Visual Studio Code extensions that you have installed: What's the easiest way to get this list? it will take me all day to type them all up.

Final Checklist

Please remember to do the following:

• Search the issue repository to ensure you are reporting a new issue

• Reproduce the issue after disabling all extensions except the AL Language extension

• Simplify your code around the issue to better isolate the problem

[FBakkensen]

I am experiencing the exact same problem when trying to debug page 408.

As an additional information I have the same problem when trying to view the source code from the new AL Explorer in VS Code for page 408 og report 7323, while it works fine for other objects.

[PooyaKharamesh]

This issue misses the information mentioned in the template. To help us get to the issues faster you must provide all the information in the template.

Please provide the following info
AL Extension version
Server extension version

[FBakkensen]

AL Extension: 11.0.787898
Server: BC Saas Sandbox 22.0.54157.54644

[MarjanChabukovski]

This issue misses the information mentioned in the template. To help us get to the issues faster you must provide all the information in the template.

Please provide the following info AL Extension version Server extension version

AL Extension: 11.0.787898
Server: BC Saas Sandbox 21.5.53619.53813

[fvet]

It seems to be related to slashes included in the object name, at least that's my guess ...

[MarjanChabukovski]

It seems to be related to slashes included in the object name, at least that's my guess ...

Who's going to fix it I wonder? I logged a case with Microsoft and they referred me here :)

[MarjanChabukovski]

I was debugging OnPrem BC ver 19 today and I got the same issue so the BC version is not the culprit here. It seems that @fvet was right. I'm getting No content avail for any objects with / in their name. AL Extension is 11.0.787898 and VSC is 1.77.0

[NKarolak]

It seems to be related to slashes included in the object name, at least that's my guess ...

Then this is related, it seems
#7369

[thloke]

This is actually something on the VSCode side. I've raised the issue with them, but I'll ping them again.

microsoft/vscode#172108

[minaskats]

This is still an issue also for "Inventory Posting To G/L" and the report 1002 "Post Inventory Cost to G/L".

[minaskats]

This starts to be a very big problem for us. We can not debug the CODE of A/L making it a lot harder to solve our customers problems.