EasyPopulate 4.0 Support Thread

[chadderuski]

Excellent add-on - and "almost" does what I need, with one show-stopper exception!
I may be listed as a New Zenner, but have been using OSC since it began 14 years ago!


We have multiple systems that need to talk to each other to synchronize data - including our "composer" for products, and have to do the synchronization using the products_id, not the products_model.

The products_model "could", but seldom changes. The products_id (which also syncs to the POS for inventory) is the one constant!

Is there an easy way to force the products_id field to be respected and used as the products key?

Hi Dan!

This will take some thought... EP4 has been coded to work specifically on the products_model. Not saying that the products_id is not doable, but there would be some significant coding for this.

Have you looked at Langer's Easy Populate Advanced 3.0.3? He does allow use of the products_id, but I don't know much more than that.

I can put this on the "slate" but I am terribly busy with several paid projects and the "day job", so I don't know just when I could get to it...

Sorry if that's a disappointment. I really do want to make EP4 a complete product for us zenners.

-chadd

[DanT]

Hi Dan!

This will take some thought... EP4 has been coded to work specifically on the products_model. Not saying that the products_id is not doable, but there would be some significant coding for this.

Have you looked at Langer's Easy Populate Advanced 3.0.3? He does allow use of the products_id, but I don't know much more than that.

I can put this on the "slate" but I am terribly busy with several paid projects and the "day job", so I don't know just when I could get to it...

Sorry if that's a disappointment. I really do want to make EP4 a complete product for us zenners.

-chadd

I certainly understand Chad! I have those restrictions myself!

I looked at the Langer 3.03 and it doesn't seem to do as much error checking etc, so I've put a couple mods into yours!
It doesn't do everything, but from testing it "prefers" the model for ALL changes.
On additions to the DB, IF the v_products_id column exists in the import file, it will use that ID #.
If there is an insert conflict (duplicate ID), you already throw the error.

I'm sending a PM with some "minor" changes (snippets only) that appears to do what I need. Possibly others could need too.

Let me know what you think!

Dan