uProduce API and FILE_ADOR_NAME setting

[Heather Wright-Porto]

Please see attached PDF for screen shots and more details.I also have a support ticket open with XMPIE support.

I am trying to use the API to output in separate files by ADOR name.  

If I remove the highlighted below, it works fine and uses the default file name assigned such as Heather_r1.pdf, Heather_r2.pdf, Heather_r3.pdf.

However, with the highlighted in place, where Layout is in fact one of our ADOR Names it fails.

I have tried others like Sequence_Number which is a number and unique, but anything I use in this parameter fails.

So, I may be missing some other parameter or setting that MUST be used in combination of using this FILE_NAME_ADOR parameter.

Any ideas?

Thanks,
Heather

                 <Parameter>

                     <m_Name>PDF_MULTI_SINGLE_RECORD</m_Name>

                     <m_Value>True</m_Value>

                 </Parameter>

                 <Parameter>

                     <m_Name>FILE_NAME_ADOR</m_Name>

                     <m_Value>Layout</m_Value>

                 </Parameter>

[Heather Wright-Porto]

 Hey there,

Looking for some help with the uProduce API. JobTicket.setOutputInfo to be exact.  I have opened a ticket with XMPIE support but they typically are not helpful with API support.

Thanks,
Heather

Inside the setOutputInfo api function, I am using these 2 parameters. And it will successfully output in separate files IF I do not use highlighted parameter, FILE_ADOR_NAME.  Layout is a valid ADOR name. I have tried others, but any will fail.  Is there some other setting that must be set or disabled to use the FILE_NAME_ADOR?

[Quinton Smith]

Hi,

 

Your approach appears to be correct.

 

Noticed that your FILE_NAME_ADOR, m_Value is [Layout] and not [layout] as seen here:

 

 

Not sure if this might be the reason that it is failing, but thought to mention it.

--
You received this message because you are subscribed to the Google Groups "XMPie Interest Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xmpie-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xmpie-users/ca409f31-db44-4cff-824a-917ba2c0336b%40googlegroups.com.

[couch]

A good way to debug these kinds of issues is to process the document via the dashboard the way you want it done and take note of the job id in the job centre.

Then go to the SQL server, XMPDB2 database.

Run this query, replacing 123 with the id of the good job:

SELECT jobParams FROM XMPie.TBL_JOB WHERE jobID = '123'

Save the XML job params to a text file "good.txt"

Repeat the query with the job id created with your API application which is not giving the right result. Save it as "bad.txt"

Then use text comparison tool like beyond compare to see exactly what is the difference between the two good/bad job tickets. It will point you to what is missing/wrong in your api jobticket.

[Heather Wright-Porto]

@Quinton Smith.

YES. THANK YOU.  It was the case-sensitivity. [Layout] and not [layout]

This is now resolved.

--

You received this message because you are subscribed to the Google Groups "XMPie Interest Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xmpie-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/xmpie-users/b643651a-d620-46c4-b9fe-72e8fbac08ba%40googlegroups.com.