Dynamics Community Forum Thread Details

AL Debug with Microsoft cloud Sandbox environment

I have a custom procedure for Customer Custom field integration table mapping I want to debug because it is currently not working. The breakpoint inside the procedure is not hit. I am working inside vs code with a microsoft cloud sandbox environment.

This is my attach configuration inside launch.json:

{

"name": "Attach: Microsoft cloud sandbox",

"type": "al",

"request": "attach",

"environmentType": "Sandbox",

"environmentName": "Development",

"breakOnError": true,

"breakOnRecordWrite": false,

"enableSqlInformationDebugger": true,

"enableLongRunningSqlStatements": true,

"longRunningSqlStatementsThreshold": 500,

"numberOfSqlStatements": 10,

"breakOnNext": "WebServiceClient",

"tenant": myTenant

}

I was able to start it VS Code debug with Ctrl + Shift + F5 and choosing the Microsoft Cloud Sandbox. When I make a modification inside the customer card the code stops inside the 1302 codeunit "Customer Mgt.". After I press F10 to continue the code execution it does not stop in my procedure. If I use the Attach: Microsoft Cloud Sandbox option, it does not even stop in codeunit "Customer Mgt.".

I am using the information on this site for setting up the debug: Attach and Debug Next - Business Central | Microsoft Docs

This site is used for setting up custom field integration mapping for Customer Table: Custom Integration with [!INCLUDE[cds_long_md](../includes/cds_long_md.md)] - Business Central | Microsoft Docs

If I set the breakOnRecordWrite on true there is no reaction in vs code. Code does not stop in any codeunit.

Is there an option that I have not set in launch,json or Business Central Sandbox environment ?

Quick Links

Leaderboard > Small and medium business | Business Central, NAV, RMS