Tips, Tricks and Warnings for using the InDesign Plugin

eDoc does not behave in the same way as InDesign.   While it does save time to upload your template via the Indesign plugin, you will definitely need to make adjustments to your template after uploading into eDoc.  Please see below for some tips for using the InDesign plugin:
1) Grouped Boxes - Select all boxes on each page of the InDesign document and make sure all are ungrouped before uploading the the document to eDocBuilder. Grouped boxes may cause the template to behave unexpectedly.
2)  Bleeds - Do not set a bleed in your InDesign file.  Create your document to be the size of the finished piece plus the bleed.  After importing the document into eDoc, set the bleed on the Template Info tab.  Setting the bleed in the InDesign file will cause fields to shift out of position when uploaded into eDoc.

3)  Tracking - In eDoc, tracking on the format tab of a field is designed to imitate Quark Xpress. This formula uses the standard kerning value, as defined in the Quark help file. Quark takes the font size and calls that an em space. The kerning is 1/200 of the em space. So to convert this to a value the system uses this formula: (fontsize/200)*kerning.  InDesign measures tracking in 1/1000 em, not 1/200 em like Quark. Therefore the formula would be (fontsize/1000)*tracking if you are taking the value from InDesign.  You may need to adjust your tracking in eDoc.

4)  Leading - Set the leading of the first line of text in your InDesign document to zero.  This will prevent your text from shifting down in the field after uploading it into eDocBuilder.
5)  Field Size - InDesign will allow text to go past the field size, eDoc does not. For example, if you create a field that is 10pts high, InDesign allows you to enter in 12 pt font in the field.  When uploaded into eDoc, the system will either force fit the text within the field or no text will show.  If you see changes in your font size or kerning, check to make sure that your field is tall enough to accommodate your font size plus leading.  Also, check that you do not have "Force Fit" turned on.  This setting is found on the Format tab of the field in eDocBuilder.  If this is turned on, it will compress the text to fit within the field - shrinking the font size, kerning and leading.
6)  Field types - Do Not Use Check Boxes, Combo Boxes, List Boxes, Buttons, Radio Buttons or Signature Fields.
7)  Default text - Please note that at this time rich text and Unicode plain text is not supported with the InDesign plugin.
8)  Fonts - The plugin will upload fonts.  However, if your InDesign file uses font types that are unsupported by eDoc, then the font will not be imported.  Fonts must be in Open Type (.otf), True Type (.ttf), or Type 1 (.pfm + .pfb) format to be used by eDoc.
9)  Export to PDF settings - The plugin makes use of the PDF export settings in InDesign.  It will use the settings from the last time you exported to a PDF from InDesign.  Make sure that your PDF export settings do not include any bleed settings and that it is set to export all pages.
10)  Updating an existing template with the Plugin
a.  The InDesign document is associated to the eDoc template via a GUID, not by name. Changing the name of the InDesign template does not break this link.  Once you upload an InDesign document to a template, that document is associated to that template going forward (unless you choose to Upload as New from the InDesign plugin - as opposed to updating existing.  Upload as New links the InDesign file to the new template). We recommend saving a copy of the InDesign document before uploading into eDoc at each revision stage.
b.   If you update an existing template with the plugin, you will update it to the settings used on the fields in the eDoc window (Type, Name, Prompt).  Most of the time this isn't an issue, but things like Image Picker Groups and Static Text or Field Scripting are not in the type selection. So if you update the template it will change to Standard Image and Text Area for each of those fields using Image Picker and Static Text or Field Scripting.