I am trying to get a solution to create cascading dropdown when uploading new documents to an SPO document library.
I saw a post for 3 column drop down to SP lists, but I believe a custom list does not act the same as a custom library (But I may be wrong :)).
We are scanning in all our paper docs to a library, and moving all docs from shared drives to the same library.
In the library I added 3 required columns, Location,source,doctype
There can be up to 20 sources and each source can have up to 50 doc types.
Each location has it's own combonation of LOC/SOURCE/DOC TYPE
I am trying to reduce errors by cascading from location to source to doctype
When Location#1 is chosen I only want the sources for that location, then when the location and source are chosen I only want the doc types for that loc/source combo.
Is this possible? If so, can anyone point me to a how to blog?
The available cascading dropdown example are all related to SharePoint list.
A sample one:
By the way, for the library in PowerApps, currently it is not possible for PowerApps to get the related file, it would only be available to work with the corresponding property field.
I have an app where I used distinct to create cascading dropdowns. All works fine, except that the field is not updated in my sharepoint list. The property UPDATE is set to Dropdown.Selected, but even the persona selects the right value in the dropdown the value is not updated in the sharepoint list.
I read something that Distinct only returns a table with one unique column called "Result" with no ID. Is that the reason why the UPDATE property odoes not work.
How do I make sure the value selected through the cascading menu will update in the sharepoint list?
Check it out!
Check it out!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand