My users don't like the “the saved data cannot be shown” message.
And in the context of this application I understand that.
The search for a Person on a screen with a cardlist and a form.
If they don't find the Person they must add it.
After adding the Person they get this message.
But they want to see the Person they just added.
I tried making a task with a process flow that replaces the normal Add button.
Very simple, a task without template, then process actions for Clear Filter, Add Row (capture Person ID), Change Filter (to Person ID).
Work fine, but I cannot disable the standard Add button without als disabling the Add Row process action.
So this is not the solution.
Then I tried without a task, starting the process flow with Add Row. But then I cannot do a Clear Filter first.
So it is Add Row, Clear Filter, Change Filter.
But that gives met the dreaded message “the saved data cannot be shown” again.
While it IS SHOWN ON THE SCREEN.
How do I accomplish this?
(On Universal 2024.3)
Suppress "The saved data cannot be displayed" message
+2- Vanguard
- 15 replies
Best answer by Arie V
Basically the logic should check if the data is not visible AFTER the Process Actions for Clear/Change Filter have been applied and then only throw the message if still relevant.
Note that implementation of the Idea is halfway, but not the highest priority at the moment. Especially testing all the possible combinations is quite a time-consuming exercise.
+4Hi
There are a few options to bypass the problem you've mentioned:
- Have the task create the person, completely bypassing the form altogether.
If that means the task would be too big, depending on the amount of data you need to add when adding a person you can also try this:
- Use a task to add simply a person, including possible mandatory columns
- Pass the output from executing the task, including the created person_id to the process flow
- Use the change filter process action to the newly created person_id
Let me know if that works :)
If not, then the option to suppress the notification you mentioned might have to be an idea for the future.
Kind regards,
Renée
+2- Vanguard
- 15 replies
Hi Renee,
Your approach will probably work, but I don't think it is what we are looking for.
- It is a lot of columns that I don't want to define as task parameters.
- Persons was just an example, we would need to do this for nearly all our 1500+ tables.
I found an Extended Property RowNotFoundAction with possible values None, ShowInfoMessage (default), FilterRow.
FilterRow could be the behaviour that we want.
But this property does not have seem to have any effect on Universal 2024.3
+12
Basically the logic should check if the data is not visible AFTER the Process Actions for Clear/Change Filter have been applied and then only throw the message if still relevant.
Note that implementation of the Idea is halfway, but not the highest priority at the moment. Especially testing all the possible combinations is quite a time-consuming exercise.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.