Restrict Effort Field Updates in Resource Assignment (SPM Module)

We are currently migrating projects from our custom application into the SPM module through a script. Many of our existing projects have some resources whose contract_hours include decimals (e.g., 230.5 hours), and we want to map these values exactly to the Effort field on the Resource Assignment record when the script creates it.

The issue is that, for some records, the Effort value is not retained as entered — it gets rounded or changed, which seems to happen because of some backend Business Rule or configuration.

Here's an example: (please find a video in the attachment for better understanding)

Project X
Resource Y has 1,248.38 hours in the custom module.
- Expected Effort in SPM: 1,248.38
- Actual Effort populated: 1,248


I initially suspected the property com.snc.resource_management.allocation_interval_minutes might be influencing this. Its default is 60. When I tested with different values (6, 12, etc.), the Effort field returned inconsistent numbers, for example:

With value 60: Effort = 1,188
With value 12: Effort = 1,200.4
With value 7: Effort = 1,200.7

It seems like there’s some calculation or rounding logic tied to this property or another rule.

My goal is to allow these exact decimal values to be inserted into the Effort field during migration without impacting the normal behavior of resource allocation or daily allocations.

Could you please advise how we can achieve this, or if there’s a way to temporarily bypass this rounding logic during data migration?

Some other effort hours mismatches I also faced, please find screenshots in the attachments.


Is there a way to temporarily prevent the Effort field from being auto-updated (and allow decimals) during migration, without affecting other functionality?