We’ve added a UD field to the ProjCstHistory record. Obviously, updating this record during Revenue Recognition through binding is not an issue but I’d like to update a couple hundred historical records. However, there is no method to update an existing transaction. I would guess this would be the same for tables like PartTran. Any clever ways to update these types of user-defined fields in tables that store historical information?
I usually do these via BPM. Write some BPM code to query and update the records you want and then hang the BPM of an inconspicuous method and trigger it. (My favorite is ABC Code. GetNew)
I am not using the BO’s for updating the UD Fields in this case as a one time run but I am using the BPM tools which have some built in protection against screwing the pooch so to speak. Don’t query the xx_UD table just query the main table the _UD fields come with it.
Do you prefer Canadian beer now that you’re with Six-S? Being close to Canada here in Detroit, I can bring you some Molson or Labatt’s Insights in Nashville…
I love my Canadian neighbors to the south of Detroit! Wait until the Letterkenny show makes it to the States. It will satisfy your inner-twelve year old.
I’m aware of the Epicor requirement to not update SQL tables directly, and wouldn’t do so. BUT, the question is in reality how different is doing what you describe? If you’ve written bad code, whether you press Execute query in SQL server mgmt. studio or GetNew on ABC code, the results will be the same!
I agree Mark. One time, in an Education Database long, long ago, I was “learning” to write Progress BPMs and all of the sudden, every Part had the same description… (I thought I had a ‘where’ statement somewhere around here…)
But back to the issue at hand, what other options are there for updating a UDF in a historical record if they are not available via an adapter or a BO? Architecturally, Epicor would have to add a method to each Business Object that exposes only the UDFs and that’s a lot of work for not a lot reward.
It might be a good feature for DMT to be able to do this kind of an update in a structured/safer manner…