Dataverse for Teams - Designer needs up to 30 minutes before I can start working on the app

[Bjoern_J]

Hi,

I have one app in DV4T that takes for ever to load, until "the ants have stopped running", I can't work on the app:

I have this issue now for about 2 weeks, and I tried everything I can think of:

• in-private session
• different browsers (edge, chrome, firefox, vivaldi)
• in Teams client

It only happens with this one app, and I have no idea what is triggering it or what the designer is waiting for.

Does anyone have an idea why this happens or how I can resolve it?

Because this is my main project atm, I always have to plan around the loading time to when I can work on the app.

Thanks a lot in advance!

[timl]

Hi @Bjoern_J 

I would check your app for any embedded resources.

Have you uploaded any large videos or image files through the media section? If so, this would slow the loading of the app in the designer, and will explain why it affects this one app only.

[EricRegnier]

Hi @Bjoern_J,

If it's not what @timl mentioned, then maybe the best approach would be to submit a Microsoft Support ticket at https://admin.powerplatform.microsoft.com/support of type performance. They are usually pretty quick and can get the telemetry from the backend. Cheers 

[Bjoern_J]

Thanks @timl for your quick response and sorry for my late reply.

I don't have any videos or files in my app, it's all just text.

What I do have thou is a gallery of Font Awesome icons for design purposes.

Within the gallery the icons image property is set to the data:image/svg+xml property.

Like this:

"data:image/svg+xml," & EncodeUrl(
    "<svg viewBox='0 0 100 100' xmlns='http://www.w3.org/2000/svg'>
    <style>
      
@font-face {
    font-family: 'Font Awesome 5 Free';
    src: url('data&colon;application/font-woff2;charset=utf-8;base64,...

I might remove the code fro the image property just to give it a try later, so anyways thanks for the hint!

[Bjoern_J]

Thanks @EricRegnier for the idea, already thought about it and meanwhile I guess I'll give this a try.

[Bjoern_J]

Here's an update on this topic.

I never contacted support yet, might still do just to validate what I figured out by now.

I am using lots of layout containers on several screens to make the app super-responsive, which works really nice if not super fast.

I even use them within my galleries for easy layout purposes which works like a charm.

So I finally figured out, that if I delete 2 of my screens, no matter which, as long as the contain many layout containers, the app starts immediately.

I tried this with all sorts of my screens, worked every time.

So I assume that there is some sort of layout container limit which causes the delay.

I also tried removing content within containers to check if it might be some lookup or something else, but the only real success in getting rid of the startup delay was when I deleted 2 screens, or also just deleting the containers in those screens.

Maybe this helps someone else, or maybe someone has an idea what could cause it in regards to containers.