Word layout from the scratch

[radovandokic]

Hi all,

I created report in AL, from the scratch, and set path to the Word layout.
After Build (Ctrl+ Shift + B) is executed, empty Word file is created:

I open Word doc, and insert 2 fields from dataset and 2 text constants:

I save document, build, publish and install app.

When I run report, only text constants are visible:

When I try to insert new layout in Custom Report Layouts, I get this error/warning:

Same result is when I leave Word doc empty, and modify layout through Custom Report Layout page.

So, dataset is not linked with word layout. I tried many combinations, always is the same.
Is this a bug, or I am missing (doing wrong) some steps?

I am using the latest image: bcinsider.azurecr.io/bcsandbox:ca

Idea is to have report ready for use, not users should do design from the scratch.

Thanks,
Radovan

[radovandokic]

Hi,

Do you have any update?

[StanislawStempin]

The problem seem to be spaces and periods in the dataitem name. The workaround is to use data item names that don't require double quotes.

In your case please try renaming
dataitem("Gen. Journal Line"; "Gen. Journal Line")
to
dataitem(Gen_Journal_Line; "Gen. Journal Line")

[radovandokic]

You are right, now it works.

Thank you for support,
Radovan

[ALGitHubBot]

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 26357.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

[ALGitHubBot]

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 26357.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

[ALGitHubBot]

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 26357 and VS Code Extension Version 2.1.68780.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

[kine]

One observation connected to this issue:

1. New word layout was created, app with the report was published into container
2. New custom layout based on this word build-in layout was created
3. Update layout was used on the Custom Layout page
4. Layout was modified, saved, imported
5. Running the report with the layout was giving correct result
6. The layout was exported and imported into the App source code instead the original empty one
7. App was rebuilded and published
8. The layout stopped to work and it seems that differences is that the namespaces have different format regarding the spaces - sometime they are replaced with underscore, and sometime not.

We tried to rename the report to name with underscore instead spaces and it helped. Now it is stable.

Result: The AL is not consistent in using underscore/spaces in the namespaces.

Extension version used: 3.0.124247