In Integration Builder, use a database to supply the name of the template based on a value in a drop file S’abonner

0
Avatar
Trey Holst

I would like to simplify the label printing by taking the part number in my drop file and looking up the template to use in a database.  I have a stored procedure that accepts a part number and returns the template name.  What I don't know how to do is assign that value to a variable in Integration builder to be able to populate the condition on the Print Document step.

7 commentaires

0
Avatar
Pete Thane
Actions pour les commentaires Permalien

If the label name is contained in the trigger file I know you can achieve this but if the template name is contained in the database that the label is linked to I am not sure if that is possible directly from an Integration, with the drop/trigger file containing the database lookup as that action is performed in the label template itself.. 

You may be able to set up Process Builder to achieve this but I have not "played" enough with this yet to get my head round how all that works. 

0
Avatar
Rick Borst
Actions pour les commentaires Permalien

Trey, did you find a solution that you'd be willing to share?

0
Avatar
Trey Holst
Actions pour les commentaires Permalien

Unfortunately I have not had a chance to dig into this again so I just have a very long list of parts as a condition in the Print Document section under the Action tab using the PartNumber is any of ....  It works, but if you have a really long list you may want to use the "Conditionally, based on expression" and have multiple "OR" conditions so you can add multiple entries to keep it manageable (e.g. A-E, F-M, N-Q, R-Z).

0
Avatar
Pete Thane
Actions pour les commentaires Permalien

If your labels are all the same physical size you could create a label with multiple templates in it and then include conditional printing for each template such as

 

0
Avatar
Pete Thane
Actions pour les commentaires Permalien

...sorry meant to add:

That way you can configure your integration to open your master label with each template designed differently but still all linked back to your database and the condition you used would be set to filed in the database that holds the template/label name. 

You can also extend the conditional actions to make separate Data Entry forms for each template too if that were required, although possibly not if you are triggering the printing via an integration 

0
Avatar
Rick Borst
Actions pour les commentaires Permalien

sorry for the dealy Pete and thanks so much for your follow up. I'm just getting back to this today and follow up.

0
Avatar
Trey Holst
Actions pour les commentaires Permalien

I like this idea.  There is definitely more flexibility to setting variables on the label than in the integration builder.  If I remember correctly, you do have to be aware of your naming convention because it causes issues if you have the same object name even if it is on a different tab.  I'm going to give this a go with one of my labels and hopefully I will get it to work from the database.

Vous devez vous connecter pour laisser un commentaire.