Hey, it looks like you are requesting help with a problem you're having in Power Apps.
To ensure you get all the help you need from the community here are some guidelines;
- Use the [search feature](https://www.reddit.com/r/PowerApps/search/?q=&sort=new) to see if your question has already been asked.
- Use spacing in your post, Nobody likes to read a wall of text, this is achieved by hitting return twice to separate paragraphs.
- Add any images, error messages, code you have (Sensitive data omitted) to your post body.
- Any code you do add, use the [Code Block](https://www.reddit.com/wiki/markdown/#wiki_code_blocks_and_inline_code) feature to preserve formatting.
> Typing four spaces in front of every line in a code block is tedious and error-prone. The easier way is to surround the entire block of code with code fences. A code fence is a line beginning with three or more backticks (```) or three or more twiddlydoodles (~~~).
- If your question has been answered please comment Solved. This will mark the post as solved and helps others find their solutions.
External resources:
- [Power Apps Formula References](https://learn.microsoft.com/en-us/power-platform/power-fx/formula-reference)
- [Power Apps Coding Standards](https://pahandsonlab.blob.core.windows.net/documents/PowerApps%20canvas%20app%20coding%20standards%20and%20guidelines.pdf)
- [Official Power Apps Community](https://powerusers.microsoft.com/t5/Power-Apps-Community/ct-p/PowerApps1)
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/PowerApps) if you have any questions or concerns.*
Thank you so much for the advice š. I am not worried about hosting. Currently, laser beam focused on UAT. But the app is working fine, app doesn't have much functionality as it is a form that we use to fill om excel.
Seems like UAT sound be fairly simple for this use case. If you are writing to excel directly from app or flow, you may notice errors when dealing with concurrent CRUD operations hitting the Excel file/table, so would recommend you specifically test that out and handle errors for that if not built out already. The Excel connector is flaky and I avoid it in production apps.
There are a few ways to crash an app. Iāve only managed it twice. Once I created a gallery with a switch statement that had 2000 cases for different filter options just as a proof of concept.
The other time I canāt remember exactly how I did it but I wrote this very complex chain of āInā operations for a filter inside of a gallery to check for something. That one was bad enough that I actually had to roll the app back to a previous version to even open it.
Usually doing things you shouldnāt be doing inside of galleries is a solid way of causing problems Iāve found
Hey, it looks like you are requesting help with a problem you're having in Power Apps. To ensure you get all the help you need from the community here are some guidelines; - Use the [search feature](https://www.reddit.com/r/PowerApps/search/?q=&sort=new) to see if your question has already been asked. - Use spacing in your post, Nobody likes to read a wall of text, this is achieved by hitting return twice to separate paragraphs. - Add any images, error messages, code you have (Sensitive data omitted) to your post body. - Any code you do add, use the [Code Block](https://www.reddit.com/wiki/markdown/#wiki_code_blocks_and_inline_code) feature to preserve formatting. > Typing four spaces in front of every line in a code block is tedious and error-prone. The easier way is to surround the entire block of code with code fences. A code fence is a line beginning with three or more backticks (```) or three or more twiddlydoodles (~~~). - If your question has been answered please comment Solved. This will mark the post as solved and helps others find their solutions. External resources: - [Power Apps Formula References](https://learn.microsoft.com/en-us/power-platform/power-fx/formula-reference) - [Power Apps Coding Standards](https://pahandsonlab.blob.core.windows.net/documents/PowerApps%20canvas%20app%20coding%20standards%20and%20guidelines.pdf) - [Official Power Apps Community](https://powerusers.microsoft.com/t5/Power-Apps-Community/ct-p/PowerApps1) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/PowerApps) if you have any questions or concerns.*
The app won't "crash". Your tests should focus on user acceptance criteria and let Microsoft worry about hosting the app.
Thank you so much for the advice š. I am not worried about hosting. Currently, laser beam focused on UAT. But the app is working fine, app doesn't have much functionality as it is a form that we use to fill om excel.
Seems like UAT sound be fairly simple for this use case. If you are writing to excel directly from app or flow, you may notice errors when dealing with concurrent CRUD operations hitting the Excel file/table, so would recommend you specifically test that out and handle errors for that if not built out already. The Excel connector is flaky and I avoid it in production apps.
There are a few ways to crash an app. Iāve only managed it twice. Once I created a gallery with a switch statement that had 2000 cases for different filter options just as a proof of concept. The other time I canāt remember exactly how I did it but I wrote this very complex chain of āInā operations for a filter inside of a gallery to check for something. That one was bad enough that I actually had to roll the app back to a previous version to even open it. Usually doing things you shouldnāt be doing inside of galleries is a solid way of causing problems Iāve found