Notifications
Announcements
Hello everyone,
One of our customers is experiencing an issue with the Business Central SaaS AT Version (BC 25.3). When they open the report 11108 "VAT - VIES Declaration XML" and run it with the desired filters, it generates a faulty XML file. Specifically, the tags <SOLEI> and <DREIECK> are affected. These currently show a "1" but since the beginning of March, a "j" should be entered instead of the "1".
Is there already a solution for this? Manually editing the XML would only be a temporary fix.
Source: https://www.bmf.gv.at/dam/jcr:08ae63a8-0fc4-4818-a960-f76c9404ad26/BMF_Dokumentenversion_Zusammenfassende_Meldung.pdf https://www.bmf.gv.at/services/finanzonline/informationen-fuer-softwarehersteller/softwarehersteller-erklaerungen-und-antraege.html
<SOLEI>
<DREIECK>
"j"
"1"
Create a Report Extension: Copy Report 11108 to a custom report (e.g., Report 50108) to avoid modifying the standard object.
Adjust Boolean-to-Text Conversion: In the VATReportLine data item, add a function to convert boolean values to "j" instead of "1":
VATReportLine
local procedure FormatBoolToJN(Value: Boolean): Text[1] begin if Value then exit('j'); exit('n'); end;
Update XML Generation: Replace the existing Format(...) calls for SOLEI and DREIECK with the new function:
Format(...)
SOLEI
DREIECK
// Existing code (example): // XmlElement.AddElement('SOLEI').AddText(Format(VATReportLine."VIES Sole Proprietor")); // Updated code: XmlElement.AddElement('SOLEI').AddText(FormatBoolToJN(VATReportLine."VIES Sole Proprietor"));
Note: Test the custom report in a sandbox environment before deployment. If Microsoft releases an official update, revert to the standard report.
Compliance: Aligns with BMF guidelines requiring "j" (yes) or "n" (no) for boolean XML fields.
Reference: Use the BMF documentation links provided to validate XML structure requirements.
Hello Mr. Saif Ali Sabri,
Thank you for your response. In the Austrian version of the MS Base App (Microsoft_Base Application_25.5.30849.31230.app), the report 11108 still includes XMLFile as the data type and Scope('OnPrem'). As a result, I cannot simply copy the report. The tag for 'SOLEI' is also still added as follows:
XMLFile.Write(StrSubstNo('<SOLEI>%1</SOLEI>', 1));
in the function WriteXMLData(). As a precaution, I have debugged this report, and it still executes this code in the cloud.
Create a custom XML export logic to override the hardcoded values, as direct report modification isn't feasible due to Scope('OnPrem').
Scope('OnPrem')
Build a Custom XML Generator: Replace the XMLFile-based code with cloud-compatible XML generation (e.g., XmlDocument):
XMLFile
XmlDocument
procedure GenerateCorrectedXML() var XMLDoc: XmlDocument; RootElement, SoleiElement: XmlElement; begin XMLDoc := XMLDoc.Create(); RootElement := XmlElement.Create('VATDECLARATION'); XMLDoc.Add(RootElement); VATReportLine.FindSet(); repeat SoleiElement := XmlElement.Create('SOLEI'); // Use the actual field value and format to "j"/"n" SoleiElement.AddText(FormatBoolToJN(VATReportLine."VIES Sole Proprietor")); RootElement.Add(SoleiElement); until VATReportLine.Next() = 0; XMLDoc.WriteTo(XmlWriter); // Use XmlPort or save to Blob end;
Override the Export Process:
Create a new report or codeunit that replicates the data collection of Report 11108.
Use XmlDocument/XmlPort to generate XML with <SOLEI>j</SOLEI> instead of hardcoded 1.
XmlPort
<SOLEI>j</SOLEI>
1
Deploy the Custom Solution: Instruct users to run the new report instead of the standard Report 11108.
Workaround Until Microsoft Fixes the Standard Report:
Export the data from Report 11108, then use a PowerShell/Python script to replace <SOLEI>1</SOLEI> with <SOLEI>j</SOLEI> in the XML file.
<SOLEI>1</SOLEI>
Compliance: Ensures alignment with BMF’s requirement for j/n boolean values.
j
n
Key Note: Monitor Microsoft updates for a permanent fix and revert to the standard report once available.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
OussamaSabbouh 1,585
Khushbu Rajvi. 780 Super User 2025 Season 2
YUN ZHU 712 Super User 2025 Season 2
