On visible is not fired on Production environment

[Gopika_gp]

Hi,

We have recently deployed a solution into a target environment when we play that application the On visible is not firing up so some details are not visible on the screen as we have used collections. Those collections will be populated on On Visible of the screen. But other screens are working fine this issue is seen only in two screens. And when the app is played for the first time we get an error like this 

Error when trying to retrieve data from the network: List not found clientRequestId: e80205d0-e339-4da7-9518-a00c5b79242c serviceRequestId: e80205d0-e339-4da7-9518-a00c5b79242c

We are clueless why we are getting this error and on visible is not firing. It will be a great help if anyone knows the cause and solution for this. I really appreciate any help you can provide.

[Amik]

@Gopika_gp -

1. What is your data source?
2. Are you using environment variables?
3. I assume the error does not occur in source environment?

[Gopika_gp]

Hi,

The datasource is Sharepoint. Yes, we are using environment variables, which are of type datasource. The error doesn't occur in the dev (source) environment.

[Amik]

@Gopika_gp - have you verified the environment variable in the target environment is returning a data source?

"List not found" suggests it is not.

[Gopika_gp]

Yes checked them I just opened the app in Production environment it shows a message like this

is there anyway to rectify this because in production we cannot open the app and save the app again.

[Amik · Accepted solution]

@Gopika_gp - ensure you do not have any unmanaged layers in your production solution. If you have any, please delete them.

If you do not have any unmanaged layers, you now need to directly open the production version of the canvas app

and identify what is causing the error with your variable.

It is possible to edit a canvas app deployed into a production environment as part of a managed solution by accessing that app directly from the Apps section.

Once you open the app in edit mode, the data source pane will still "display" as if it is still pointing to your DEV/UAT data source, but you can rest assured when looking at the data, the canvas app is actually looking at your PROD data. This is a defect Microsoft are aware of with environment variables deployed across different environments in a Solution.

https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/solutions/dataverse-environ... 

Note that any modification you make, save, or publish will not impact the canvas app hosted in the managed solution. No unmanaged layers will be created in the Solution.

Regarding the error. The error is appearing because you’re populating a variable with a record which contains a specific schema, but then somewhere else in your app, you’re also populating that variable with a record which has a different schema.

Some classic checks

If you’re using an Edit Form control, it is important to understand that an Edit Form contains two important properties, the DataSource property and the Item property (which is used to display a specific record).

The schema used in the DataSource property, and the schema returned in the Item property must match. For example, suppose you’re populating the Item property with a Gallery selection (or a variable created from a Gallery selection), if the data source used in the Gallery Items property is different than the data source used in the DataSource property in the Edit Form control, you will receive an error.

This occurs very often when users leverage the AddColumns or GroupBy function when modifying the Items property of a Gallery control. If you have modified the schema of the Gallery like this, then the data source used in the Gallery Items property, and the data source used in the DataSource property of the Edit Form, will no longer match.

To accommodate for this, it is best to use a LookUp function in the Item property of the Edit Form. For example:

Lookup(yourdatasource, ID = Gallery1.Selected.ID)

Or if using a Variable:

Lookup(yourdatasource, ID = MyVariable.ID)

If your scenario matches the above description, it is important to restart the app after you make this correction in order for the error to disappear.

Other checks

• Ensure you do not have a Global Variable and a Collection with the same name.
• Follow a process of elimination to identify which variable declaration is causing the error. For example, navigate to the variables menu to view how and where the variable is being defined, and then for each declaration of that variable:
  
  1. Delete one instance where the variable is being being declared/initialised.
  2. Click save and restart the app and check if the error still appears.
  3. If the error continues to appear, repeat for the next variable declaration and keep restarting the app.
  4. Once the error disappears, you can then pinpoint exactly which declaration was causing the error, and then investigate further.