PowerApp Requires Premium Incorrectly

[homol]

I have built a canvas app that interfaces with a single SharePoint List.  The only thing special I'm doing with it is that it was an empty gallery that I painstakingly built out for the customer.  Now, all of a sudden, I'm getting warnings about needing a Premium license, even though I only have this one connector.  Can anyone help me to debug?

[mdevaney]

@homol 
Create A Ticket with Microsoft Support.  The community members are not Microsoft employee and likely cannot help with your issue.

Go to this page and click 'Create A Ticket' at the bottom of it.

https://powerapps.microsoft.com/en-us/support/

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

[homol]

@mdevaney thanks for such a prompt response.  The link below seems to just bring me right back to this forum.  Is there a special trick to getting a proper support ticket going?

[homol]

Nevermind.  I'm an idiot lol.

[v-xida-msft]

Hi @homol ,

Have you added a Flow connection within your canvas app?

According to the screenshot that you mentioned, it seems that you have added a Premium connector in your canvas app. Please check if you have added a Premium connector in your canvas app before, and then remove it.

Also please check if you have added a Flow connection (Power Automate flow connection) in your canvas app. If you have added a Flow connection in your app, when you run your app, you would be prompted to confirm or update any connections on which the flow relies. So if you added a Premium connector in your flow, and you added the Flow connection in your canvas app, then your canvas app would be recognized as "Premium" License designation canvas app rather than "Standard" license designation canvas app.

If you do not add a Flow connection or a Premium connection in your canvas app, but the issue still show up, please consider edit your canvas app's configuration file based on the following steps:

Spoiler

1. Export the app from power apps, comes down as a compressed folder (zip), extract the contents of the compressed folder (zip).

2. In the root of the compressed folder you will find a "manifest.json"  in there is a "dependsOn":[] section, simply remove the unwanted parts.

3. Then under --> Microsoft.PowerApps --> apps --> {someID} --> {someID}.json . Open up the json file and look for the section 

"connectionReferences":{} again remove the unwanted parts, I removed all the connections.

4. Then save the modified files back the folder with the same names,then making sure the manifest.json file and Microsoft.PowerApps folder are in root, compress(zip) the folder back down. 

5. Import/Upload the compressed folder (zip) back into power apps. 

then open up the json file and look for the section "connectionReferences":{} ,  check if there are some Premium connection listed there, if yes, please remove the unwanted parts. After that, save the modified files, and re-import your compressed folder (zip) back into your canvas app, then check if the issue is solved.

Please check and see if the following thread solution would help in your scenario:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Data-Connection-Won-t-Delete/m-p/593998#M186...

If the issue still exists, please consider submit the support ticket for further help through the following link:

https://admin.powerplatform.microsoft.com/support

Best regards,

[homol]

Kris,

Your advice on looking into the manifest.json and {SOMEID}.json was extremely helpful.  While it did not actually show that I was using a Premium connection, it did however show that I had somehow started referencing AI portions of the CDS.  At some point in my debugging I recall accidentally referencing something from the AI Builder in Intellisense and then removed it from the app, however it looks like the reference remained.  Here's what the databaseReferences section looks like in my {SOMEID}.json:

      "databaseReferences": {
        "default.cds": {
          "databaseDetails": {
            "referenceType": "Environmental",
            "environmentName": "default.cds"
          },
          "dataSources": {
            "43b0dc67-68af-47ae-9a9c-9e69d396ba3e": {
              "entitySetName": "msdyn_aimodels",
              "logicalName": "msdyn_aimodel"
            }
          }
        }
      }

I'm assuming that I might be able to fix this by reverting the databaseReferences section to this:

"databaseReferences": {}

Is that correct?  Also, does the zip or any of its files need to be versioned or renamed in any way before trying to upload it back?  Does it need to be minified in order to successfully re-upload?

Thanks for your help thusfar!

[homol · Accepted solution]

In case anyone else runs into this, here is what I had to do.  Big shout out to @v-xida-msft , who set me on the correct course of action, but I had to do something a little different.

Basically, I was referencing the AI model in the CDS, but nothing in the UI indicated that.  

I had to Export the app to .zip.  I unzipped that package, drilled into {SOMEID} folder and opened up {SOMEID}.json.  I left the file minified and found this section of json:

      "databaseReferences": {
        "default.cds": {
          "databaseDetails": {
            "referenceType": "Environmental",
            "environmentName": "default.cds"
          },
          "dataSources": {
            "43b0dc67-68af-47ae-9a9c-9e69d396ba3e": {
              "entitySetName": "msdyn_aimodels",
              "logicalName": "msdyn_aimodel"
            }
          }
        }
      }

I updated the json to look like this:

"databaseReferences": {}

Then I had to rezip the file, from the folder that the manifest.json resides in.  Then I was able to re-upload the package and tell it to update my app, and then my app was back to a Standard license.  Woo Hoo!

[v-xida-msft]

Hi @homol ,

Is the solution I provided above helpful in your scenario?

If the solution I provided above is helpful in your scenario, please also consider go ahead to click "Accept as Solution" to identify my reply as helpful.

Best regards,

[MartinsDogoh1]

After several hours of googling around, this resolved my issue. Many thanks

[Blipstar]

Thank you so much, this worked perfect for me also!  was worried I was going to lose months of work.

😄