You’re offline. This is a read only version of the page.
Previously, we used the Power Automate Power Apps (V2) Trigger and the Canvas App Attachments Control to save documents to SharePoint List Attachments with the following original formula:
ForAll(DataCardValue9.Attachments As Document, upload_file.Run(new_case_return, {contentBytes: Document.Value, name: Document.Name}));
After discussion, Microsoft officially recommended using a nested file field instead:
ForAll(DataCardValue9.Attachments As Document, upload_file.Run(new_case_return, {file: {contentBytes: Document.Value, name: Document.Name}}));
This solution works correctly in our development lab environment, but it does not function in our existing Power Apps applications.
Based on this situation, we have the following questions and would greatly appreciate your clarification:
What is the rationale for adopting the new syntax?
Will applications using the old syntax (without the nested file field) be forcibly updated to the new version?
If a forced update occurs, will it cause existing applications to break?
If a forced update is inevitable, what are your recommended mitigation strategies? (Considering that many of our existing applications rely on the old syntax.)
We kindly request your help in verifying the compatibility and update mechanism between the old and new versions and providing relevant guidance. Thank you for your assistance!
Unresolved Questions:
2. Will applications using the old syntax (without the nested file field) be forcibly updated to the new version?
3. If a forced update occurs, will it cause existing applications to break?
4. If a forced update is inevitable, what are your recommended mitigation strategies? (Considering that many of our existing applications rely on the old syntax.)
Stay up to date on forum activity by subscribing.
#1
WarrenBelz
146,513
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,681
Most Valuable Professional
Share
Report
All responses (
Answers (