asked on January 27 Show version history

Hello,

I had an email convo with Support that was very helpful, but wanted to get some input from others who have done something similar. I have a customer who is changing ERP systems, and things like vendor names/IDs and GL codes will be changing (these are dynamic fields right now). This would mean that existing documents will start showing dynamic field validation errors once the source data is changed, which makes sense - that's the point of dynamic fields.

I don't want the old data to be in the new source data just to avoid this error. My initial thought is to rename the current fields in Laserfiche to something like "Vendor Name OLD," then drop them from the template. This would retain the values, and users would need to know that the field name has changed if they're going to perform field searches. Then, I can add new fields to the template with the same field names as before, configure the dynamic fields with the new source data, and hopefully be good to go.

That's what I'm planning on doing, at least. Certainly possible I'm overthinking it. Has anyone been through something like this and can offer some insight as to what they did to avoid dynamic fields errors?

Thanks!

0 0