PROD PowerApp pulling data from UAT

(0) Share

Report

Posted on by SudeepGhatakNZ

14,394 Most Valuable Professional

Hi all,

One of my customers is experiencing a weird behavior in one of their production APPs.

The APP is deployed as part of a solution that uses environment variables to fetch data from SharePoint.

Suddenly some users (not all) have reported that the PROD app is fetching info from the UAT SP Site.

At this point, I don't believe the problem lies with the environment variables, as it seems to be affecting only a specific group of users. I'm reaching out to gather insights and ideas on what might be causing this issue.

Your thoughts and suggestions on troubleshooting or potential root causes would be greatly appreciated.

@WarrenBelz @Pstork1 @LaurensM

Thanks

Sudeep

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

The first thing I would check is the Dataverse table where the environment variable definitions and values are stored to make sure that all the users have access to the tables to read the values. The second thing I would check is to make sure that the users are actually running the latest version and not running an older version that points at the UAT tables. What is the Data Source for the App? Dataverse, SharePoint or something else?

Was this reply helpful? Yes No
SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

Thanks @Pstork1 for responding.

My data store is SharePoint, and I initially inspected the environment variables, but everything appears to be configured correctly. What makes this situation particularly perplexing is that it's occurring exclusively for specific users.

In the past, I never encountered the necessity to grant users any additional access to Dataverse tables. This is an unprecedented occurrence. I went a step further and had the users conduct tests in incognito sessions, but unfortunately, the issue persisted.

As I'm running out of ideas to explain this unexpected behavior, hence reaching out to seek additional insights or suggestions.

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

If the data source is SharePoint then you shouldn't need to give any permissions to Dataverse. The only other thing I can figure is that the users are using an old version that points to the wrong SharePoint site.

Was this reply helpful? Yes No
Verified answer

SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

@Pstork1 ,

I successfully resolved the issue and wanted to keep you informed.

The root cause of the problem stemmed from the fact that, upon the user's login to the UAT app, Power Apps generated a SharePoint connection. Strangely, this same connection was being utilized when attempting to connect to the PROD app.

In theory, creating a connection should result in a generic SharePoint connection not explicitly linked to a particular site (as I initially believed). However, it appears my assumption might be incorrect.

To rectify the situation, we took the approach of deleting the user's SharePoint connection directly from the Power Apps landing page. Subsequently, we had her log in to the prod app again. Upon doing so, a prompt appeared, asking her to create a new connection, and, lo and behold, the issue was resolved!

Thanks for your time with the investigation!

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (1)

Report

Are UAT and PROD in the same environment? Connections are based on the environment. So the expectation is that when you import the solution into a new environment the user will generate a new connection. Since UAT and PROD were both using the same connection I assume they were both in the same environment. The system is designed to work with separate environments and will do the behavior you saw if used in the same environment.

Was this reply helpful? Yes No
SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

No. The UAT and Prod environments within the Power Platform are distinctly separate. The user has been designated as a Basic user in both environments. She had been participating in UAT testing.

I assumed that when the user initially accesses the application in the Production environment, she should be prompted to create a new connection. However, it appears that this expected behavior did not occur. So, I am still not sure what happened. But recreating the connection resolved the issue.

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

If they are separate environments then the user must create a new connection. Connections are environment based and can't span environments. So I'm not sure how the one user ended up with a Connection pointing to the UAT data source. Of course if they had an existing connection in the Prod environment that pointed to the UAT data source from some other app then they wouldn't be prompted to create a new one.

Was this reply helpful? Yes No