We have standardized on having all our part updates happen on our 300 company and then the updates propagate to our 400 company when the multi-company direct process runs. We are working on rolling out a web site and condition the updating of the web site parts list with the “webPart” flag on the part master. The person that needs to update this is only authorized to our 400 company. Given the challenges of Epicor’s security groups, I do not want to authorize them to our 300 company.
I created an external BAQ and dashboard that looks into the 300 company parts list and bypasses the security. I then changed this into an updatable BAQ but I can’t use the default BPMs to update Part because the user is not authorized. My way around this is to write C# in a custom BPM to update the field in the other company. This works fine although I am most likely not doing this the best way.
My challenge is now the update has happened in 300 but because of my “backdoor” method, this has not triggered the process to kick off the Multi-company process to update 400. My BFI method (Brute-force-and-ignorance) was just to hard code the 400 company in a second update and this did the trick.
I am sure there is a better way to do this that would use the business objects and avoid my second update. Any ideas?