System name on application imported to Dataverse for Teams

(0) Share

Report

Posted on by HFG

516

Hi all,

I just imported an application from Dataverse to Dataverse for Teams. The system name is showing as "new_nameofapplication_63222" rather than the usual system prefix and the name of the application. I assume this is normal? Will this application work in just the same way as others created directly in the environment?

Are there any known issues with working with applications that have been imported into Dataverse for Teams? Any useful documentation I can read? The only official stuff I have found is this: https://github.com/MicrosoftDocs/powerapps-docs/blob/live/powerapps-docs/teams/import-solution-in-teams.md

I would like to move an application that is currently using SharePoint over to Dataverse for Teams so I'm hoping I can import it rather than having to rebuild completely.

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report

Hi @HFG ,

Please check out the following article (https://docs.microsoft.com/en-us/powerapps/teams/import-solution-in-teams) for details.

The biggest thing to consider is if you used any of the standard dataverse entities or enabled "Activities", this will be a challenge as it will not import as not supported.

No other issues that I know of right now.

Hopefully this is what you were looking for.

Thanks,

Drew

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report
Hi @HFG,

To answer your question about the prefix it's because you exported the solution with another publisher; specifically the default publisher. You can edit the publisher on the solution (select solution --> Settings) and create a new one for your organization with the right prefix or update the default publisher with the desired prefix. Once done, delete the table(s) (and other solution components) in Teams and re-import the solution.

Apart from what Drew mentioned on limitations, the other limitations in DV4T I know of are:

Calculated / rollup fields are not supported

More limitations on column types

Canvas app controls are more limited

Security model is much more limited

No access to API / SDK (besides Power Automate)

Here's the doc on limitations: https://docs.microsoft.com/powerapps/teams/data-platform-compare#:~:text=In%20Dataverse%20for%20Teams%20and,apps%2C%20chatbots%2C%20and%20workflows.&text=The%202%2DGB%20capacity%20provided,1%20million%20rows%20of%20data.

So basically the components in your solution cannot contains any of those limitations...

Hope this helps!

Was this reply helpful? Yes No
HFG 516 on at

Like (0)

Report

@EricRegnier and @dpoggemann

Thank you both for your replies, very helpful. I'm off to do some reading on solutions!

Thanks!

Was this reply helpful? Yes No