Yes, I did run the trace while updating a job using the JobEntry form.
- I opened the form, then started the trace.
- Typed in my job number.
- Clicked Op 40 in the tree view.
- Clicked the Resource in the tree view.
- Selected a new Resource Group from the list.
- Copied the value from the Resource Group box.
- Clicked on Op 40 in the tree view.
- Pasted that value back into the operation Description field.
- Saved the job.
- Ended the trace.
I am using the trace parser.
When I compared the Update methods, I noticed a lot of fields marked as changed contain a decimal “0.000” and the return show integer “0”. I don’t need to worry about these right?
Otherwise I see a few other fields changed that I am not accounting for, including:
<ProdLabRate>
<SetupLabRate>
<EstLaborCost>
<LaborEntryMethodDesc>
<PrimaryProdOpDtlDesc>
<PrimaryResourceGrpDesc>
<PrimaryResourceGrpID>
<PrimarySetupOpDtlDesc>
<ShowStatusIcon>
<StdBasisDescription>
<StdFormatDescription>
<ResourceGrpIDDescription>
If I am understanding correctly, I need to set the values for these fields using a process similar to what I outlined above. Right? When I use the setfield widget do I set the ttResults field or the tableset field?
Thanks a bunch!
Nate