Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Print to ELO with BC
NAVFuchs
Member Posts: 76
Hi,
my customer has an ELO archive to which documents are printed through a printer driver. The Document has
special control chararacters, so ELO know what document it is. With NAV 2017 this worked fine, as the
printer output is textual based and therefore can be interpreted by ELO.
The same print from BC results in a way that textual parts of the document leads to grafical parts in the document and
therefore the control characters cannot be found any more in the document.
In the preview, you can still select parts of the text, when you send it to the printer e.g. "Microsoft print to PDF" or other printer
driver, the text are "converted" to grafic. If you save directly to PDF or "Send to..." and select "PDF-Document" it is still "text-based".
So it looks, that BC handles documents to print in a different way. Is there a trick how this can be solved or other ways to go through?
( I know there is the possibility to save the pdf in a path for ELO, but this leads to other problems and configurations"
best regards,
Markus
my customer has an ELO archive to which documents are printed through a printer driver. The Document has
special control chararacters, so ELO know what document it is. With NAV 2017 this worked fine, as the
printer output is textual based and therefore can be interpreted by ELO.
The same print from BC results in a way that textual parts of the document leads to grafical parts in the document and
therefore the control characters cannot be found any more in the document.
In the preview, you can still select parts of the text, when you send it to the printer e.g. "Microsoft print to PDF" or other printer
driver, the text are "converted" to grafic. If you save directly to PDF or "Send to..." and select "PDF-Document" it is still "text-based".
So it looks, that BC handles documents to print in a different way. Is there a trick how this can be solved or other ways to go through?
( I know there is the possibility to save the pdf in a path for ELO, but this leads to other problems and configurations"
best regards,
Markus
0