I've very recently started using PowerApps and my first test was taking the Support Request Template and altering it to better fit my organisation.
One of the changes i've made is to allow admin users to submit forms on behalf of other users. When admins do this, they have the option to update the task status of the call to "COMPLETED". This essentially just removes some of the faff that we would have to do (create the ticket, go back to the menu screen, find the ticket, edit the ticket), and also means users will recieve less emails.
The problem i've encountered is that when we mark the form as "COMPLETED", the call is added to our SharePoint list and it appears as completed, however the flow that sends the email resends the previous ticket created to the previous user instead of sending the new ticket.
(E.g. John Smith is an admin and created a ticket at 12:00 on behalf of "User A". "User A" is sent a confirmation ticket upon creation of the ticket with some of the ticket details.
John Smith then creates another ticket at 12:30 on behalf of "User B" and this time marks it as complete. Flow then resends the first ticket to "User A", then sends the new ticket to "User B".)
All I have done is set the default "Task Status" card (from the "Help Desk" template) to visible for admin users.
The flow is also the same as the one created in the "Help Desk" template.
To make it even more frustrating, when I preview the app in the editing page, it works perfectly. When I publish the app, the above issue occurs.
Any insight as to why this may be happening would be much appreciated.
Thank you for your response.
I have reviewed the guidance you sent but unfortuantely it hasnt helped with the issue i am encountering.
The powerapp is 99% working. The only fault is when I unhid the "Task Status" field on the ticket creation page. If the value if changed from "Not Started", the flow does not function properly.
For example, I have just created a new ticket which was given the auto ID value of "252". I marked this ticket as "Completed" from the ticket creation page as I had unhid the "TASK STATUS" selector (which is hidden by default). however instead of the flow running with the value of the ticket that was just created (252), the flow ran using the ID of the last ticket I created, which in this case had the ID 210.
Happy to provide any screenshots as requried if that would make this easier to understand.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Join us for the next call on June 15, 2022 at 8am PDT.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.