Updating primary bin in pilot and I keep getting this error. “There are no records in the table ds.Part”
To my knowledge all the BPMs are disabled.
All of a sudden started doing it. Does it for every part. Not sure what the cause could even be.
Can you provide some more context?
Not much more to provide, I hate to say it.
I take any part in pilot. I can update the part, description, pricing, etc. But when I get to the warehouse tab, that is when I get the error. This is only when I change something and I try to save it.
In this case, when I set the primary bin or change it, it’s popping this error. Works fine in production.
It just started today out of no where. Changed nothing. No new BPMs. In fact all BPMs are turned off.
I created a ticket with epicor already as I have no clue what’s going on here.
It looks like you might have some kind of customization in there. You confirmed no BPM, but what about customizations?
Just tried it in Dev as Base only and it still did the same thing.
I recall you doing a lot of messing around with parts trying to debug setting a part bin.
Make a brand new part or choose one you for sure have never touched and see what happens.
I’m letting support fiddle with it right now. Seems like something else is going on. I’ll report back with what they did.
Created a new part and I get the same issue.
Do you have another environment. Let’s say test. Try what you are doing in a different environment and if it persists in test too, then need to dig more.
Did you do any changes related to fields present in ds.Part table? If then try to revert it back and try again. It happened once to me for part and it showed issue in order entry. If it is customization then revert it back too.
See if it works.
So I found out the cause but not the solution.
Epicor couldn’t figure it out and they wanted to bring on a consultant to resolve it. I said just load production over pilot and be done with it. They did that and sure enough error went away.
I went back to what I was doing which was creating a BPM using restsharp and bam it’s back again.
After testing I figured out the reason why.
I’m setting a variable “PartNumber” and I use the “Set Argument/Variable” widget. The “Set Argument/Variable” is the problem. I remove that and I get no error.
Here is the simple BPM:
Here is the Set Argument/Variable widget.
It’s only job is set variable PartNumber to dsPartRow.PartNum.
Shouldn’t be an issue but for some reason it doesn’t work. I tried it in pre-processing and post-processing.
Solution was to go another route on the expression.
I used dsPartWhseRow.PartNum instead and no issue.