Home > User Voice > Info and prevent saving if there are outstanding http requests

Info and prevent saving if there are outstanding http requests
0

MVP

Hi,

I've cases where one choose field updates another choose field. If the data source is not a SQL database this can take some time.
Setting the first field takes about 1 second, (1) in the attachment.
Getting picker search results 540ms
Validate picker control 460ms

The setting and validation of the target field (2) takes again 1700ms and another 390 ms for executing a form rule.
Setting target form field first choose field 1160ms
Validate picker control 611ms
Setting own target fields 0ms
Form role on value change 390

Since the second field could be modified manually afterwards, I can't simply change the field type.


In these cases, it would be great, if there's some information that there's are outstanding http requests. I'm aware, that it will be difficult to find a balance between to much/to few information.
But at the same time it's strange when the user sees the value of the second field in the popup search and then the target field values do not reflect the value for a longer time, without any information.

There's also one drawback I've encountered.

If the user doesn't wait and hit's save / uses a path, the target fields may not have been updated yet.

Best regards,
Daniel

Nobody has replied in this thread yet.