I have just been battling a strange error. When I called a certain page in our solution all clients just crashed, hard.

So what was different with this page? It’s card page, connected to a list page, works great when users double click on a record in the list page the card opens – Works perfectly.

But if I open the card page directly with PAGE.RUN(xxx,SomeRec) all clients crash!

In the stack trace, I could see something about subforms (DoBuildSubform) so I suspected the culprint was a pagepart (Yeah, Microsoft still calls it “forms” in their code) and I removed my subforms. Sure enough, now everything worked. I inserted each pagepart until I found the offending page.

The sub page uses the BusinessChart control, and it was the only control on that page. Running the sub page didn’t reviel anything strange, so I was puzzled for awhile …

Poking around, I suddenly notices that the PageType was a ListPart, with only one control on the page. There was really no listable thing to do, so I tried to change it into a CardPart instead – and sure enough, now everything worked 🙂

TL;DR Putting a control add-in on a ListPart subpage can crash all clients when the parent page is called with PAGE.RUN or PAGE.RUNMODAL – Change to CardPart to fix crash.

Something weird happened on my local dev machine. I have a standard installation of NAV2018 installed, currently upgraded to CU2. Suddenly I’m swamped with messages about the default tenant is not accessible.

In C/Side:

In the Modern Development Environment:

The strange this is that if I restart the service tier I can download symbols once, but if I try to download them twice, I’ll get the above error the second time?

From the RTC:

Then I tried to use the PowerShell Sync-NAVTenant command:

And boom, this because I had deleted a table without syncing the database (I was working on an uplifting concept).