I upgraded outsystems data grid web forge component from v 2.17.0 to 2.18.1. I am having issues in my data grid traditional application after upgradePlease see the below images regarding a column whose value was valid before the upgrade but is not being treated as invalidBefore upgrade:
After Upgrade:
The structure that is being used to create the data for data grid has this column marked as non-mandatory
Hello @Arsalan farooqui
You can add to your column's AdvancedFormat input the value "isRequired: false" and you'll be able to overcome that behavior and control it as you wish.Hope it helps!
AdvancedFormat
"isRequired: false"
Cheers,GM
Thanks @Gonçalo Martins , this solution is working! Do you have any idea why it started behaving like this after upgrade?
Hello @Arsalan farooqui,
To make this more efficient and collaborative for the community please share a sample OML where that issue can be reproduced. That way someone from the community can take a look without investing more time in implementing the use case.
Hi @Gonçalo Martins , It is a production application and I am unable to create the same scenario in a dummy OML. Please refer the below textℹ Information
This was mentioned in the release notes of latest version of Outsystems data grid web forge component. I believe this is what is causing the issue. The thing is, I am unable to find how to mark the fields non-mandatory. Please help me with this.
Hi @Arsalan farooqui,
Without access to an oml replicating your use case, I won't be able to help.
Can you please share oml? so I can check at my end. It is very hard to find the issue with such a small information. after upgrading there are lots of possibilities so its hard to pinpoint the issue.