Skip to main content
Solved

How to change UOM for Projects Module

  • January 23, 2025
  • 3 replies
  • 34 views

We currently have our Empty Item UOM in our Project Preferences as HOUR. We are trying to change this so our Empty Item UOM will be EA. 

When we try changing this, we get an error message saying that the Project records could not be updated due to at least three fields being empty; Allocation Rule, Billing Rule, and Branch.

Going through all our projects, the only project with empty values is Project X, the Non-Project code Project.

We are unable to update the fields of project X since it is a non-project, and were unsuccessful in trying to make the three fields not required through a customization project by both removing the PXDefault from the fields and trying PersistingCheck = PXPersistingCheck.Nothing. Any help would be appreciated, our next step is putting in a ticket.

Best answer by jeremiahjohnson

@Heidi Dempsey We figured out a roundabout solution, so we no longer have access to the trace. We ended up unpublishing all our customizations, since if the error cannot be duplicated, then we must have something related to those fields in our own customizations. While everything was unpublished, we were able to save the change without the error and re-publish our customizations 

View original
Did this topic help you find an answer to your question?

3 replies

Heidi Dempsey
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • 269 replies
  • January 23, 2025

@jeremiahjohnson  Could you please show the trace?  Also, have you or your partner entered a case?  I also see that your colleague Rebekah posted.  I had replied to enter a case since we cannot duplicate in sales demo.  We would be able to look at the trace, customizations, data etc.   I am not sure which screen the third screen shot is from.


  • Author
  • Freshman III
  • 2 replies
  • Answer
  • January 24, 2025

@Heidi Dempsey We figured out a roundabout solution, so we no longer have access to the trace. We ended up unpublishing all our customizations, since if the error cannot be duplicated, then we must have something related to those fields in our own customizations. While everything was unpublished, we were able to save the change without the error and re-publish our customizations 


Heidi Dempsey
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • 269 replies
  • January 24, 2025

@jeremiahjohnson  Thank you for the update.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings