Unanswered

Cascading dropdown values visible in edit mode but not visible once App is published.

(0) Share

Report

Posted on by Sumeesh

Hello All,

My app reads and writes data from the SharePoint list. For the last week, all worked perfectly reading and updating the data.

Then 2 days ago I had to make some changes in my cascading dropdown columns in the App which I have done in edit mode.

Once I made the changes, I refreshed the data source for the App and the data got reflected in the cascade dropdown. Then I saved and published the App.

Since then I cant see those data in the cascade dropdown in publish view.

So I again opened the App in edit view but the data is not visible in the cascade dropdown. Again I refreshed the data source, the data got reflected. But the same data is not reflected in cascade dropdown once I publish the App.

I have tried to delete and add again the data source in the App edit mode, but still, the issue persists once the app is published.

A) First Issue:- While in Edit mode of the App, every time I have to refresh the data source so that values can reflect in the cascading dropdown. (Note:- Data source for the App is SharePoint and all the values are constant in SharePoint)

B) Second Issue:- Once I can view those cascading dropdown data value after refreshing the app in edit mode, then as I publish the app I can't view those data.

Any other suggestions which would save me having to build the app again from scratch because already many of my team members used the App two days ago while it was working fine and data got collected in the SharePoint. Making the App from scratch will make me input all that previously filled data to fill again.

Both issues snapshot attached.

Thanks and Regards,

Dropdowns not wor...

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

v-yutliu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Sumeesh ,

I've made a similar test based on your description. However, my drop down did not have the problem like yours.

I've reported this issue to our product team.

If there's any reply, I will leave message here.

Thanks for your feedback!

Best regards,

Was this reply helpful? Yes No
Sumeesh 70 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-yutliu-msft

Is there any issue with cascading dropdown if we use data source of high, Because the data source (SharePoint) I am using has high number of the dataset.

Sharepoint Datasource for my App:- 357 items in CPC Target datasource which is less than compared with (AM&DM) items

Powerapp Edit mode:-

Edit mode of App:- As you can see the highlighted data sources and their items(datasets). The data source CPC targets with high number of data set (items:- 367) is not working for me and other two data source less item datasets is working perfectly once i publish the App.
Or should I change anything in Power App settings:-

Snapshot:- Advance setting of App
Need to resolve this issue as soon as possible.
Thanks for the help.
S

Was this reply helpful? Yes No
Sumeesh 70 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-yutliu-msft

Any reply regarding this issue from the product team.
Can we do Webex or Microsoft teams call where I can show the issue by sharing my desktop?
Please share your id if it's okay for you.
Actually I am trying to solve this issue for the last 3 weeks. Need help as soon as possible.

Thanks and Regards,
S

Was this reply helpful? Yes No
corey_msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
@Sumeesh

We have just completed a hot-fix to restore the previous behaviour when evaluating rules for Form controls and their children after a form is reset or its default mode is changed (new, edit, view). The issue would most commonly cause list controls (CombooBox, Dropdown, ListBox) to intermittently fail to load data.

Please save your apps(s) and re-published for the changes to take effect.

Studio versions containing the hot-fix are as follows:

3.20053.25 (PROD moderate release ring)

3.20061.28 (PROD US regions)

3.20062.20 (PROD rest of regions)

3.20063.11 (PROD preview regions)

We are sorry for any inconvenience this has caused.

Was this reply helpful? Yes No