We have a client that has a financial period as user defined field that is receiving an object reference error when upgrading to 24R1. I have verified the data is saving in the database, and I have tested different FinPeriodID selectors on different screens with the same issue. We have a case open, but I wanted to see if anyone else has a workaround.
+13Please find the attribute attached which is used a UDF in sales order
if you are still facing an issue, one of the customization packages causing the issues
Thanks for the quick response. We had the PX.Objects.AM.FinancialPeriod DAC in a previous version but in 24R1 we receive the same error even without customizations published.
Thanks,
Kurt
+13Did you try rebooting? 😉
+8There are no customizations published. I replicated in 24R1 demo system.
Kurt
+16There are no customizations published. I replicated in 24R1 demo system.
Kurt
Agreed
I can confirm it is still an issue in 24.106.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
