cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
HFG
Advocate III
Advocate III

System name on application imported to Dataverse for Teams

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-te... 

 

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

2 ACCEPTED SOLUTIONS

Accepted Solutions
dpoggemann
Super User
Super User

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

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

View solution in original post

EricRegnier
Super User
Super User

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:

  1. Calculated / rollup fields are not supported
  2. More limitations on column types
  3. Canvas app controls are more limited
  4. Security model is much more limited
  5. 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%20Team....

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

Hope this helps!

View solution in original post

3 REPLIES 3
dpoggemann
Super User
Super User

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

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew
EricRegnier
Super User
Super User

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:

  1. Calculated / rollup fields are not supported
  2. More limitations on column types
  3. Canvas app controls are more limited
  4. Security model is much more limited
  5. 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%20Team....

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

Hope this helps!

HFG
Advocate III
Advocate III

@EricRegnier and @dpoggemann 

 

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

 

Thanks!

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

365 EduCon 768x460.png

Microsoft 365 EduCon

Join us for two optional days of workshops and a 3-day conference, you can choose from over 130 sessions in multiple tracks and 25 workshops.

Users online (3,076)