Power Platform Community Forum Thread Details

Error App Sharing

Hi there, below I have provided a description/translation of the errors encountered by the user whom I shared the App with. I have given them access to the sharepoint site and list, the powerautomate flow, the published version of the App and access to my environment. I did these things now, so I'm not sure if after having done these things, the person will finally have full access to the app. Ps. the error messages stem from the old version of the app which strangely they have access to, when I share the link to the App with them, even though I am working on the latest version, and I click on share link from the latest version, but for some reason the link is to the old version. Would there be someone that could help me out here? Thank You.

Screenshot 1 (Field reference is not supported)

This error indicates an issue with a reference in your Power Automate flow, possibly related to a field or column in your data source (Flights Database ORG):

Verify field references: Check all dynamic content in your Power Automate flow, especially references to SharePoint list columns or database fields. Ensure the fields you're referencing exist in the updated schema.
Re-authenticate data connections: Open the Power Automate flow, go to Data Connections, and reauthenticate any connections that might have expired.
Debug and test: Run the flow manually to identify where the error occurs.

Screenshot 2 (Invalid value for "text_9")

This error suggests that the flow is passing an empty value where a valid input is required:

Check the flow inputs: Look for the field text_9 in your Power Automate flow and ensure it’s populated with a valid value. If it's pulling data from SharePoint, make sure the corresponding column isn't empty.
Add validation: Include a condition to handle empty values before proceeding with the step that uses text_9.

Screenshot 3 (Field reference error repeated)

This is likely the same issue as the first screenshot. Addressing the field references in the Power Automate flow or verifying the connection to the data source should resolve it.

Quick Links