Does anybody have fairly solid methods of working around Creatio's limitation of not being able to distinguish between zeroes and missing values for number fields? This often comes up in requirements, and I haven't found a workaround that works so well that I always use it.
Some methods we've tried/considered:
- Using Text fields instead of number fields
- Obvious disadvantage of not having numeric protections/validations, both in the page layer & the backend & database side
- Values can't be aggregated into KPI widgets/graphs, unless you have some process to copy the number text into a hidden number field...
- Having a Boolean field for every number field to indicate if it should be null or zero
- Cumbersome to implement on objects with lots of number fields
- Field still displays as a zero value unless you add in custom code everywhere it appears
- BPs or Event Listener code needed to ensure these 2 fields agree, plus logic in the page/integrations needed to set the flags and make the field show nothing when the flag is set
Any other workarounds people are using that are effective? Hopefully Creatio will add this capability at some point as it is crucial for having valid data, but it feels like it would require a fairly big change to the platform, so I don't expect we'll get it very soon!
Like
0 comments