Skip to main content
Question

Implementation Dynamic values to the ZebraDesigner


Forum|alt.badge.img+9
  • Sidekick (Customer)
  • 133 replies

Hello,

 

Please, how can I input dynamic values to the label created in ZebraDesigner? In Zebra Designer, I created new label with static values, but i need to input there dynamic values, like batch no, date, company etc..

7 replies

Forum|alt.badge.img+10
  • Hero (Partner)
  • 145 replies
  • January 9, 2025

How do you intend to print the labels? Is it for batch printing for initial labeling of parts or is it going to be based on transactions, ex: at the time of receiving PO’s you want to print the relevant labels etc.

if its for batch printing and ODBC connection of some sort will be helpful. if it is for transactions, there are multiple ways of configuring the system. Ex: ZPL, or use BarTender with the integration funcitonality where a trigger will initiate the print etc.


Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 133 replies
  • January 9, 2025

Data which i want to fetch dynamically i have saved in ZPL file


Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 133 replies
  • January 9, 2025

and I want to move this data from zpl to Zebra


Forum|alt.badge.img+10
  • Hero (Partner)
  • 145 replies
  • January 9, 2025

Not too sure the below helps, but what I did was use the PO Arrival Report to print labels at receipt. Defined a report definition record and set the ZPL code as below. when a PO was receipted and the use selected Print Arrival report, the label would print. I had to set up some other stuff like the print agent, to pick files saved on a server location etc….

 

<?xml version="1.0" encoding="UTF-8"?><report-layout>   <properties>      <version>8.0</version>      <layout-type>SCRIPT</layout-type> <!--SCRIPT,XSL,XML,EXCEL-->      <plugin-class>ifs.application.reportingservices.impl.extendedformatter.scriptplugin.ScriptPlugin</plugin-class>      <output-method>BINARY</output-method> <!-- BINARY,FILE,E-MAIL-->      <output-extension>txt</output-extension>         <default-output-reference>         <binary></binary> <!-- leave empty to control this from the print dialog (it will be the physical printer connected to a logical printer) -->         <file></file> <!-- not used unless changing output-method above to FILE-->      </default-output-reference>      <full-xml>TRUE</full-xml>      <flattened-xml>         <enabled>TRUE</enabled>         <strongtyping>TRUE</strongtyping>      </flattened-xml>      <report-id>ARRIVAL_REPORT_REP</report-id> <!-- Change this to your REPORT ID -->      <report-title>Zebra Label</report-title> <!-- Title shown in the drop down, if installed via the installer -->   </properties>   <plugin>      <properties>         <mode>script</mode> <!--script,xml-->         <repeat>off</repeat> <!--on,off-->         <repeaters></repeaters> <!-- null = all rowtypes-->         <file-name>zebra.zpl</file-name>       </properties>      <data>         <![CDATA[^XA~TA000~JSN^LT0^MNW^MTT^PON^PMN^LH0,0^JMA^PR6,6~SD15^JUS^LRN^CI0^XZ^XA^MMT^PW551^LL0376^LS0^FT58,344^A0N,23,24^FH\^FDSite:^FS^FT58,309^A0N,23,24^FH\^FDActivity Seq:^FS^FT58,274^A0N,23,24^FH\^FDProject:^FS^FT59,239^A0N,23,24^FH\^FDPO Line:^FS^FT28,156^A0N,23,21^FH\^FD[@PART_DESC]^FS^FT254,272^A0N,23,24^FH\^FD[@PROJECT_ID]^FS^FT254,307^A0N,23,24^FH\^FD[@ACTIVITY_SEQ]^FS^FT255,203^A0N,23,24^FH\^FD[@OEM_NO]^FS^FT254,341^A0N,23,24^FH\^FD[@SITE]^FS^FT255,239^A0N,23,24^FH\^FD[@PO]^FS^BY4,3,80^FT101,88^BCN,,Y,N^FD>[@PARTNO]^FS^PQ1,0,1,Y^XZ]]> <!-- This can be a static script or completely dynamic (all ZPL generated in the RDF) as in this case.-->      </data>      <variables>         <variable name="PARTNO">tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:PART_NO</variable> <!-- this is what a variable looks like-->         <variable name="PART_DESC">tns:ARRIVAL_REPORT_REP_REQUEST/tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:PART_DESCRIPTION</variable> <!-- this is what a variable looks like-->         <variable name="PROJECT_ID">tns:ARRIVAL_REPORT_REP_REQUEST/tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:PROJECT_ID</variable> <!-- this is what a variable looks like-->         <variable name="ACTIVITY_SEQ">tns:ARRIVAL_REPORT_REP_REQUEST/tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:ACTIVITY_SEQ</variable> <!-- this is what a variable looks like-->         <variable name="OEM_NO">tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:CF_MANU_PART_NO</variable> <!-- this is what a variable looks like-->         <variable name="SITE">tns:ARRIVAL_REPORT_REP_REQUEST/tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:CONTRACT</variable> <!-- this is what a variable looks like-->         <variable name="PO">tns:ARRIVAL_REPORT_REP_REQUEST/tns:ARRIVAL_REPORT_REP/tns:ARRIVAL_HEADERS/tns:ARRIVAL_HEADER/tns:CF_PO_LINE</variable> <!-- this is what a variable looks like-->      </variables>   </plugin></report-layout>

Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • 133 replies
  • January 9, 2025

this is picture in zebra Designer, all are static values, If I want to display instead of static text “PartDescription” actual value of description, in your case 

\^FDPO Line:^FS^FT28,156^A0N,23,21^FH\^FD[@PART_DESC] how can I do that? 

Forum|alt.badge.img+10
  • Hero (Partner)
  • 145 replies
  • January 9, 2025

Forum|alt.badge.img+10
  • Hero (Partner)
  • 145 replies
  • January 9, 2025

Not too sure what printer you are using, is data you are going to print get sent to the printer directly?

What I have done in the past is ZPL layout is loaded as a report definition and when an IFS user prints that report (ex: PO Arrival Report as in the previous example) the data is sent to a file share as a .txt or a .prn and the print agent fetches the .txt file for spooling and prints. Printers used were ZT410 and ZT411. Labels were designed using BarTender and saved as .ZPL.

I still am not too sure how you are triggering the data to be sent to the printer.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings