+3There seems to be a dependency between the two non part usage fields quantity and transaction amount. Has anyone an idea why that is the case, and is there a way to disable this dependency?
For example, there appears an error message if a zero is saved in the transaction amount field, that informs that the quantity can not be zero.
Best answer by Shneor Cheshin
Hey
If I understand correctly, you are trying to create a NPU record with non_part_usage.transaction_amount equals to 0 (zero).
This is a validation in the code and cannot be overridden with configurations but with customisation.
Please refer to this thread
Cheers!
+28Hey
If I understand correctly, you are trying to create a NPU record with non_part_usage.transaction_amount equals to 0 (zero).
This is a validation in the code and cannot be overridden with configurations but with customisation.
Please refer to this thread
Cheers!
+3Hello
thank you for the quick answer.
Exactly that was one part of the question. Sadly it seems i have no right to view the linked page:
The other topic is that non_part_usage.transaction_amount and non_part_usage.quantity seem to be linked together. Is this also part of the code?
+28Sorry for that access issue.
The bottom line is that you are correct. These validations are managed in the code and not configurations.
The only option I know of, is writing a custom code that will override the baseline behaviour.
Cheers!
+3Thanks for clearing it up!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.