Image Import Profile vs Project Properties

  • 23 Views
  • Last Post 3 days ago
  • Topic Is Solved
MikeD posted this 1 weeks ago

Wondering which wins out in the event of conflicting selections, the Project Properties image pre-processing selection, or the image import profile selection.  Maybe they can be different for good reason.

I'm referring specifically to the "create new document" section where you can select either "for each image file" or "automatically when doc def is applied".

I noticed that a third party vendor that set things up for one of my projects ages ago has "for each image file" selected in the image import profile but "automatically when doc def is applied" selected under the project properties.  The project uses default batch types, nothing fancy at all and no issues have been reported. 

Seems that its possible to have these selections and not get any errors due to conflicting settings.  I suppose one simply dictates what happens initially (image import) while the other decides what to do after a match (project properties)?  Just looking to confirm my theory.  Anyone have any experience playing with these settings and trying different combinations?

Order By: Standard | Newest | Votes
Ekaterina posted this 5 days ago

Hello,

We've performed small testing on our side. We used multipage layout and set of one-page image files.

If "for each image file" option was used in the Import Profile and "automatically when doc def is applied" option was used in the Project Properties, then we had many one-page documents as a result. 

If “automatically when doc def is applied” option was used in the Import Profile and "for each image file" option was used in the Project Properties, then we had one multipage document.

According to that we can say, that Import Profile's settings override the Project Properites'.

MikeD posted this 3 days ago

Perfect, thank you.  That's helpful.

Close