Skip to main content

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.

 

According to the 24.110 release notes this was fixed in that build.


Hi @KurtBauer were you able to find a solution? Thank you!


I can confirm it is still an issue in 24.106.

Attribute using correct PX.Objects.AM.FinancialPeriod DAC
Sales Order receiving the error.  I’ve also included the about to show version and no customizations.

 


Hi @KurtBauer were you able to find a solution? Thank you!


There are no customizations published.  I replicated in 24R1 demo system.

@darylbowman I knew there was a reason you were featured as MVP of the month.  😀

Kurt

Agreed @KurtBauer! @darylbowman is pretty awesome!


There are no customizations published.  I replicated in 24R1 demo system.

@darylbowman I knew there was a reason you were featured as MVP of the month.  😀

Kurt


@KurtBauer are there any other customizations published? 


Did you try rebooting? 😉


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


Please 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


Reply