Share
Report
76This week I realized from my client's claims, that my flows return errors from most of all accesses through Dropbox API. And I found that there is a "wrapped" property under body object. I checked around some technical information but no clue at all so far. Is this just me or anyone have the same situations?
Here is why I beg helps in this community. I already asked DB dev community but due to this situation & their guidance I think this is not from Dropbox, but something injected by MS365 side.
I made a test flow & will describe step-by-step with images.
I made custom connectors using Dropbox API. In the image below, MS-original "List files in folder" is above (labeled as "list"), then the below "DB listFolder v1" is my custom connector (the same function using Dropbox API ver2 "list_folder").
The following is MS-original's output. As you see there is no "wrapped" under body object, as expected.
The following is my custom connector's output. There is "wrapped" under body (red underlined).
To clarify, my custom connector used to return no "wrapped" but worked fine just like MS-original connectors.
This cause targeting errors in any flows I have ever built. I would really like to know why this "wrapped" sits there, and if this is temporary change by MS365 team for some reason. Most of all I would love to know how I can keep my flows working without my effort of changing every single one of them.
I hope anyone could help me solve this!
All responses (
Answers (
