Once configured, the button on a forms widget remains grayed out ?

I'm creating a data service in OAD whose purpose is to update some information in the M3 customer file using a button configured on a Form widget.

This data service calls on the M3 CRS610MI/ChgOrderInfo api and uses the following 3 parameters as input: CUNO - SMCD and CUCL. As output, I don't have any parameters.

When I test this call in ION API Gateway or when I launch this data service directly from OAD, everything works as expected.

However, when I configured the correspond button in the Form widget, this button remains grey.

I don't understand what is missing ?

Thanks for your help

Find more posts tagged with

Accepted answers

All comments

Caitlin Porter

That looks correct to me. The button will always looked "grayed out" even when it is configured correctly. Does it not work?

0712131256598360.doc

Denis MARETTE

So it's misleading.
I thought my button didn't work because it was grayed out.
But in the end, thanks for the feedback: so my button isn't working properly.

Denis MARETTE

Hi Caitlin,

Now that I know that the grayed-out button wasn't the cause of the error, I've reanalyzed the button configuration.
And I've found the problem - I've actually swapped the 2 zones to be updated. So nothing was happening because, as a result, the value of one of the 2 zones must have been too large compared with the expected value. Too bad no error message alerted me and the error remained silent.

On the other hand, I've got another problem for you - sorry.
In the form, when I enter a new value for the first field and then enter a new value for my second field, I haven't even clicked on the button and the first field has reverted to its original value? Very strange behavior

Caitlin Porter

That is most likely because you didn't use the selected value data property, can you double check and make sure you used a property from the data grid and not from the data service:

Denis MARETTE

Thank you for your comment.
It's a point I hadn't paid much attention to because, in the various videos, there hadn't really been any reference to it.
Looking closely at the Builder Hour video, I can see that this is what you've done.
I've applied it and it works now.
But, for completeness, I've also set the button so that the refresh component is the dropdown component.

However, I've noticed that even if the update is done correctly, when the widget refreshes, it's the default record that's displayed in the widget and not the initial record selected, which had caused the transmission of its identifier via the context messages.

I select #DMTEST2 and I update the fields (2 instead of 1)

I click on the button

The widget is refreshed with fields coming from #DMTEST even if #DMTEST2 is still selected.

If i select #DMTEST1 and after #DMTEST2, I can see that my record has been correctly updated

is there anything else we can do to avoid this phenomenon? Thanks again for your invaluable help

Copyright © 2025 Infor. All rights reserved.