By using this website, you agree to our Terms of Use (click here)
I am sure I am missing something simple, but this is a case of proofreading your own term paper so many times you don't notice that you've misspelled your own name 🙂
I have created a new user field in AR303020 which is in DAC CR.Location. I was able to also add this to the CR303010 without any issues. What I need to so now is add this to the locations tab in the customer profile AR303000. I am not able to find my user field in any of the available data views. Can someone let me know how dense I am and what I am missing.
Thanks!
Hey Kevin,
You might want to try StackOverflow for this one. I'm wondering if something additional needs to be done to the graph on the Customers (AR303000) screen, but I'm not a developer so I'm not sure.
I've encountered a similar problem. Mine was a non-persisted custom field where I wanted to display a piece of detail on the Locations tab of the Customer screen (AR303000).
I believe the DAC for the locations is a projection of multiple classes, Location and Address. When I added the non-persisted field (UsrCompanyName), the field was added to PX.Objects.CR.Standalone as well as PX.Objects.CR
Since in my case this is a non-persisted field, I need to fetch the value for display. I tried using the RowSelected event, but my value just wouldn't show up, so I added the code to the custom field's Field Selecting event:
If you've already solved your issue, please post your solution. If not, hopefully the above gives you some insight.
Maybe not directly related, but this blog post also addresses a similar issue.
The problem you are having is that the Locations grid is actually pulling from a DAC called:
PX.Objects.CR.LocationExtAddress
If you extend this DAC with your field, you will see it available in the Locations grid on Customer screen. Just note that because of the way they are projecting this DAC, you will have to add a BQLField reference back to your custom LocationExt. Also, it is referring to the STANDALONE PX.Objects.CR.Standalone.Location mentioned by @jerrykurtz. You will need to make sure the field is extended twice, once normally on PX.Objects.CR.Standalone.Location, and then again on PX.Objects.CR.LocationExtAddress. In your LocationExtAddress extension, you will alter the PXDBType attribute and have the BQLField parameter point back to the Standalone field you just added. Check out their Descr field as an example:
Online Members
