Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We currently have a task to export sales order information into .txt file. However, fields (which are strings) carry text qualifiers ("). Are there any workarounds to overcome this issue?
Thanks for your time,
That depends entirely on how the data is going to be consumed later.
Flat files like TXT and CSV are the hardest to work with, and not just because you might have delimiters and special characters, i.e. line feeds and carriage returns, in the string fields, but also because there really is no standard at all. You might have a header row, you might not. Sometimes embedded delimiters like double quotes are escaped with a backslash (\") and sometimes by doubling them up (""). Even still there's absolutely no metadata in the file at all.
What matters most is that the program that uses them later is made happy. So, you have to work backward from that.
The real solution to these problems is to use a mature standard for data export, like XML.
Thanks Brandon for your input. Yes indeed, we are adjusting the export file according scripts written for barcode scanner.
Here is the solution we've managed to come up with,
If you use AsciiIo class to write text to file - it doesn't add text qualifiers.
io = new AsciiIo(fileName, #io_write);
cont = ["one", 2, "three", 4];
one 2 three 4
Business Applications communities