My app is already complete, I had to make a modification to one part of it which broke the attachments control when I saved it. If you used the default version (clicking edit on the PowerApps app list) it saves it using version 3.18114.25 right now.
The way I got it to save using the old version is by opening the app from the older IDE. (ie. use the link to the old version > Open PowerApps app > make your changes > save).
We are now trying to get this fix out within the next couple of days.
I will update this thread in that timeframe (by Monday).
This is fixed now.
Thank you all for reporting it, and for bearing with the workaround until now.
Thankyou for the prompt resolution to this issue. I can confirm that the file name is now available in the attachment control.
Hi,
in an powerapp environment of one of my customer with version 3.18122.23 I have this problem. How can I have the Fix ?
Thanks
Version 3.18122.23 is newer and hence no longer has the bug. I suspect the app just needs to be re-saved and re-published.
To see which version the app is on:
I would guess that it is older.
To fix that, open the app for editing, make any change, and save the app. Then publish that version.
Hi,
I confirm you that in previous version of apps I haven't the problem.
The problem start, in this environment, since this version 3.18122.23.
I edited the previous version and after saving version become 3.18122.23 and attachment control doesn't work (I don't see name of file).
If I come back to previous version, work fine (Name of file appear correctly)
Hi Friz;
I don't understand why you are still running into this problem.
Can you try to reproduce it in a new app?
Here are the steps:
The labels should be populated accordingly if there are any files attached, and if there are not, they should be updating as you use the app and attach / remove files.
Does that work for you?
Hi Jovan,
in datacard the control attachment work fine in this version.
I have the problem with this control if I use it inside a blank screen; in previous version work fine.
I attach a file with an example.
Friz, can you contact support / send in your .msapp + the scenario of how you are using the control. It's possible that you are using it in some way that we didn't anticipate, but that we could get re-enabled once we know the parameters.
User | Count |
---|---|
139 | |
132 | |
75 | |
72 | |
68 |
User | Count |
---|---|
214 | |
199 | |
64 | |
62 | |
54 |