[Merge Fellas Unlimited Shake] - Gesture causing infinite loop in Mobile SDK?

[kemiawa]

Hi everyone,

My team is facing a tricky issue with the Power BI Mobile SDK and we're hoping to get some community insight.

We're developing a custom feature internally codenamed "Merge Fellas". The core functionality is to allow users to trigger a complex data merge from our internal data warehouse directly within the Power BI mobile app. The trigger is a custom gesture we've called the "unlimited shake" (basically, shaking the device to refresh and merge).

The problem occurs during this merge fellas unlimited shake event. When the gesture is triggered, the DAX query runs, but it seems to get stuck in an infinite refresh loop, making the mobile app completely unresponsive and eventually crashing. We've confirmed the API response is valid.

Our debate is whether this is a known limitation of the mobile SDK's gesture handling when dealing with heavy DAX operations, or if our approach is flawed. We're trying to achieve a very smooth, responsive data refresh experience, similar to the fluid animations and data handling you might see in modern mobile applications.

For context, our UI/UX inspiration for this smooth data handling came from a PoC we saw here: https://modhello.com/merge-fellas/

Has anyone else tried to implement a custom gesture-based refresh that triggers a complex merge? Is the issue likely in our DAX logic, or is there a better way to manage the state within the mobile wrapper to prevent this merge fellas unlimited shake deadlock?

Any thoughts would be greatly appreciated. This is a major blocker for our project.

Thanks!

[v-venuppu]

Hi @kemiawa ,

I hope this information is helpful.If this answers your question, please accept it as a solution,so other community members with similar problems can find a solution faster.

Thank you.

[v-venuppu]

Hi @kemiawa ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-venuppu]

Hi @kemiawa ,

I wanted to check if you had the opportunity to review the information provided.If the response has addressed your query, please accept it as a solution, so other members can easily find it.

Thank you.

[v-venuppu · Accepted solution]

Hi @kemiawa ,

Thank you for reaching out to Microsoft Fabric Community.

Here are some Workarounds:

1.Prevent the "unlimited shake" from triggering multiple merges before the previous one finishes. This helps break the refresh loop and avoids app crashes.

2.If your merge operation involves complex or large data transformations, move the logic to a backend process like Fabric Dataflows, Azure Functions, or stored procedures.

3.Avoid triggering the report refresh as part of the gesture. Instead, refresh the report manually only after receiving confirmation that the merge completed successfully.

4.Power Automate (or Logic Apps) can be used to handle the merge operation and trigger a dataset refresh with better control and retry logic.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly.

Thank you.