Power App lags when getting ID with incremented number

[Frankyqt]

Hello Everyone,

I am developing an app that allows engineers to record attendance when working at customer's site. There is a data control requirement, where for each Check-in/Check-out set an ID must be generated. Specifically, the ID is a date concatenated with increment number. 

However, sometimes when a new set is created the app gets the old value. It happens when I Check-in/Check-out too quick. As seen in screenshot below, app gets value from increment number column (IncrementNum)

ref1

Below is how I generate ID:

1. Store 2 values: 1 for date and 1 for increment number

2. Use Power App collection to concatenate above values and set as variable. Collection is set to query the newest ID whenever a new record is created.

I believe this error might be related to Power App lagging, but if it's a technical issue is there any way to fix it? Or is there any way to optimize the method for generating ID? Thanks

[v-jefferni]

Hi @Frankyqt ,

In your screenshot of the formulas, since the two if statements have exact same condition, why not combine the two formulas together, so every time Patch to data source using the latest ID value?

Best regards,

[Frankyqt]

Hi @v-jefferni,

Thank you for replying. The reason why I separate is because I can't use both Set & Patch under one condition. But since your method does not require Set function, I think it will do.

Still I am not sure if it will solve the issue, let me try and get back to you later. 

9/19 Update

@v-jefferni It seems like the app is performing better, but the issue still persist. Please refer to screenshot below.

[Frankyqt]

Hi @v-jefferni,

I just noticed that without setting the variable (varIncrement), the increment number goes back to 1 as the value isn't stored. I'll have to revert back to Set function.

[v-jefferni]

Hi @Frankyqt ,

The number will go back to 1? Is the If statement included in other formulas? Last(Sort(DataSource, IncrementNum)).IncrementNum will get the largest number in that column and then plus 1 to generate the new number, I don't understand why it will get back to 1.

Best regards,

[Frankyqt]

Hi @v-jefferni 

I think Last function works correct. But the problem is that base is not defined (e.g start from 0 or 1), so the largest number will always be 1. 

As seen in the screenshot below, the increment number is 1 then 2, then back to 1. (2 is because I forgot to fix code in another button built on top of 1st one, so it incremented twice at the same time).

[v-jefferni]

Hi @Frankyqt ,

There was changing line of the formula in my previous function, it's

Last(Sort(DataSource, IncrementNum)).IncrementNum +1

this formula will search the biggest number in the column and plus 1.

Best regards,

[Frankyqt]

Hi @v-jefferni 

Sorry about my last post, I made wrong assumption. Your function is correct, but it's not compatible with my data control logic.

Actually, I built a power automate flow that forces data back to Blank status whenever user checks-out. This allows me to manipulate the Status column that you see in the screenshot. This is also the reason why I put increment inside If IsBlank condition, and because of that your function understand that last record is blank in this case 0 as base and 1 as increment value.

Despite that, as you have seen the main problem still persists.

Best regards,

Frank

[v-jefferni · Accepted solution]

Hi @Frankyqt ,

I don't think so. The whole Patch function is inside the same If statement with a some IsBlank condition, this is why I said the Set variable is not needed. But in the Patch function, my formula will sort the list ascendingly (it's by default so I didn't write), get the last value and plus 1, which means the base number will always be the largest number current (at the second of pressing the button to trigger the Patch function) in the list, blank fields are ignored.

Well, this formula can also write as:

First(Sort(DataSource, IncrementNum, SortOrder.Desending)).IncrementNum +1

Best regards,

[Frankyqt]

Hi @v-jefferni 

I tried the other function that you suggested. Like your first one, it's more consistent when getting ID number but occasionally still gets the old one. Please refer to the screenshot below:

When lag

When not lag

Your function included in my code:

Best regards,

Frank