I’m being asked to create an updatable dashboard from which the first (only for us) SalesRep can be modified.
Because the OrderHed table stores SalesRepList as a concatenation of all SalesReps listed, and because it stores the SalesRepCode instead of the person’s name, I am having a hard time figuring out how to make that data updatable. It also seems like I don’t have access to the OrderHed.SalesRepCode1 field from a BAQ.
Can anyone provide any guidance/direction? Thank you in advance!
The field in Order Head is SalesRepList. On the UI it’s a calculated version of that field cut up. So OrderHed.SalesRepCode1 doesn’t exist in the database, and thus, won’t exist in a BAQ
You could, theoretically, use that field as holding a single value and just updating a single sales rep. Is it the right way to do it? Not really, but it does cut out a lot of complexity if you say you will never use more than one (but we know how always and never go)…
In your BAQ you can use the Advanced Column Editor. Which can tie to a BAQ that you make to list your sales agents. You do that, because your display can be the name, while the actual value can be the repID. When you use an assembly dashboard, this will switch it out for you in the dashboard, and the updating will update the value and not the display. Plus there is no customization to make this work.
That being said, there is a BIG caveat, that if you ever do splits, this will not work, and could mess up orders that have splits. So use at your own risk.
I didn’t try adding the BAQ to a dashboard or anything, but I could not get the changes to “stick” when trying to update the BAQ via the Analyze screen. It would always revert back to the original value. I’ll have to look through it again to see what I missed.
That being said, what would you suggest as the “right” way to accomplish my goal?
The right way would be to make a list picker to handle that ~ delimited field, but that’s a super involved and a huge pain. I suppose you could make a calculated field for each of the reps 1-5 and that custom code the update to do the concatenating and splitting for you. That’s probably easier, and can be handled all server side. But it’s custom code for sure.
As far as not sticking… I don’t know how you have the UBAQ set to update, so I couldn’t tell you.