Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 3992 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I am currently doing some testing to see if the Scribe Plug-in will be suitable for a client. I have noticed that the ScribeDocSubstitute function strips carriage returns out of a field when it is sent to a Microsoft word document.

For example I have the following <<Postal Address>>

Which I am trying to replace with a calculated address field containing

123 Fake Street

Exampleville

QLD 0000

However, this is coming out as 123 Fake Street Exampleville QLD 0000

Is there any way to include the carriage returns in the substitution?

Posted

Last I heard they were thinking of working on this 'fault' which is a real frustration in what is otherwise a great tool. For some of my clients, I have got them to set up scripts in Word to replace <string> with "¶". That is, set up a calculated string at the end of each line in FMP with a given string instead of a return(¶), such as 'XXX' which is not likely to occur in normal circumstances. Then once in Word, manually do a replace of 'XXX' with '¶', or write a script in Word to do same.

Its not ideal, but all the other features and abilities this plugin offers might just outweigh this problem for you

  • 2 years later...
Posted

Hello Adrian I have the same problem. The carriage is not working when I convert the report in .xlsx format. Can you guide me how to do your suggestion above using ScribeDocSubstitute? Is there a way to solve my problem?  Thank you in advanced :)

 
Posted

Hello,

 

It is unlikely that the posters in this thread will check back to respond since it is from 2 years ago. In the future, you should make your own thread if there is not a recent one with the same issue you are experiencing.

 

But to help with your issue: do you have the latest version of Scribe from the 360Works website? v1.402 is available for download and it should contain many fixes for handling carriage returns when using ScribeDocSubstitute. Go to this page and click the "Download the current version" link to download the newest update: http://360works.com/filemaker-pdf-plugin/

Posted

Hello,

 

Thanks for your reply. Yes I already download the scribe v1.402 at install it in FileMaker Pro 12. About this  "it should contain many fixes for handling carriage returns when using ScribeDocSubstitute". How can i do this? Sorry I'm just new using your plug in and I'm not yet familliar with some function here. Can you guide me. Thank you in advanced :). I forgot to say I'm using .xlsx format to convert the report in FileMaker.

Posted

Hello,

 

There is a demo file included with your download named "How to use Scribe" that contains many examples for all the different functions of Scribe. I recommend you look at this file to get a better understanding of Scribe. It also contains documentation on the different functions that clarify how they work and what you should expect.

 

 

ScribeDocSubstitute is only meant for Word documents. If you want to replace named fields or cells in other files, use ScribeWriteValue instead. 

Posted

Hello,

 

I already create a script using ScribeWriteValue and its working in other fields but in my Address field (this is calculation field , result is text) which contain Carriage "¶" is not showing properlyi in the Excel.

Posted

Hello,

 

I've tested this and I can reproduce the carriage return not showing properly in Excel. I will be working on the Scribe plugin to fix this issue, and I will post back here when there is an update available with a fix.

  • 2 weeks later...

This topic is 3992 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.