Hey everyone, I am trying to recreate the functionality available in Job Status Maintenance in an Epicor Function. My function is as follows: [image] The first step (Job Number valid?) verifies the job number passed in exists. If it does, I run JobStatus.GetByID() and use the returned dataset to…

Check below thread, you basically need to have 2 rows when updating, the original one and the updated one. [image] Logic works in BL Tester, but not BPM Code (Mass Shipment) ERP 10 Try putting this before the second call to UpdateMaster var biTTShipHead = BufferCopy.Copy<…

Are you following the trace fully? Sometimes little things that seem innocuous can make the difference between it functioning correctly and not

Hey Aaron, First off, thanks for taking the time to respond :slight_smile: To the best of my knowledge I am. I am making the changes to the fields as shown in the trace log. Take the “Job Status - Job Engineered” trace for example. The fields that change between ChangeJobHeadJobEngineered and Mass…

I ran into something similar with a project I did, where I was setting the fields the way I thought they should be set, and then it returned the message “___ was not updated”… Those are a little tricky to diagnose unfortunately, but usually have to do with not updating something in the order in whi…

Have you try just calling Update instead of MassUpdate? I’ve never seen MassUpdate used in our environment

Thank you Tanner! This does update it but when a job is generated from MRP it doesn’t update the job number to the “firmed” job number we have set up in company config.

Boom - worked like a charm thank you Jonathan. The only challenge left for me to figure out is how to get the updated job number when a job generated from process MRP is firmed. But that’s an issue for another day! Thank you so much! Is there a way I could determine I need 2 rows for a method based…

Thank you to all 3 of you for taking the time out of your day to read through and respond. I really do appreciate it. @tanner your suggestion works flawlessly. I’m marking @Jonathan ’s as the solution since my original intent was to use MassUpdate instead of Update. Here is the “final” working code i…

Usually for server logic that makes validations or additional processing it simply looks for a record with RowMod U and goes to work, for new records you can also just send the one row. For updates however it uses the unmodified row to make comparisons as to what changed so it can keep everything in…

JobStatus.MassUpdate doesn't update Job when run from Epicor Function or REST call

Epicor ERP 10

Jonathan (Jonathan) March 25, 2021, 10:36pm 6

Check below thread, you basically need to have 2 rows when updating, the original one and the updated one.

Topic		Replies	Views
Job firming based on trace works in Rest and BLTester, but throws "update not allowed" in BPM Epicor ERP 10 bpm , rest , data-directives , swagger , bltester	10	3439	March 29, 2021
Same Code different behavior Client vs Server 10.1.500.8 Epicor ERP 10 epicor , e101500x , customization , bpms	23	6482	November 8, 2023
Service Connect - Job Status Maintenance Epicor ERP 10 e10	10	1289	December 2, 2019
REST API troubleshooting ChangeJobHeadJobEngineered Epicor ERP 10 customization	29	6014	March 8, 2023
Updating JobHead row from UI Form Customization Epicor ERP 10 customization	4	3658	May 18, 2017

JobStatus.MassUpdate doesn't update Job when run from Epicor Function or REST call

Related topics