I am trying to figure out how to tell if in the Customer Entry screen, there is already an entry.
They asked if I could stop a 2nd entry from happening.
I figured a post-processing method directive on Erp.Customer.GetNewCustIC would do it but I am unsure on how to test for data first.
It sounds like you might want to do it as a pre processing directive… if there is one already, throw exception. The data is stored in CustIC table. It can be there for customer as well as ship to records. See sample of our data pulled via BAQ below:
Yes, but my question is how do you test for existing data in the method directive? Which condition do I use? I am playing around with it now but unsure. Any help is appreciated.
If I were doing this, I would probably try to use a bpm on the preprocessing update of the Added record (the customer IC one) and then for a condition, use “number of rows in the … query is = 1” or something like that and then raise an exception telling user that they already have one customer ic in there and they can’t have more than one. Make sure to test that your bpm works for required edits (e.g. need to assign different ic, need to delete ic) to proceed ok too.
Here’s an example of one of our method direcitves (sales order update preprocessing) that uses a query row count condition.
Is there a chance you could build what I am asking for? If I see it in action, hopefully I can understand what I am missing and will be able to do in the future.
I am trying to build the BPM from Erp.Customer table, GetNewCustIC method.
If I do it from the Customer.Update, won’t that let them build it then not save? I would like to stop it from the beginning.
I am trying to stop a 2nd creation of the Industry Class in the Customer screen.
If you don’t have the time, I understand. I appreciate it that you are trying to get this through my head .