Anyone can help me?
I had an issue where in the field I was using for the file name the client was putting "/" character.
Once he stopped using / and replaced with space etc, worked fine.
Yes, i know! But this is not problem, because i don't use this character.
My problem is different. In many cases the PDF engine on FileMaker Go stop to render and save PDF.
A workaround consist to kill app and restart it, but i can't predict this behaviour.
I'm waiting for a response for FileMaker Technical Support...
Hope someone can assist.
I'd start by filtering this: CheckPoint::idConsegna & "-" & CheckPoint::idCheck to just letters, numbers, and an underscore. And I'd use Get ( TemporaryPath) instead of DocumentsPath.
Fabio, I think you might be experiencing a possible bug with FileMaker Go. I've used FM GO extensively and I find if I don't shut down and restart the iPad occasionally, FM GO starts to act flakey. Especially when generating a PDF. I suspect some kind of memory problem. A restart is the only way that I have found to solve the problem.
Hi David, the file name is only numeric like this: 00000784-00007236.pdf and i tried to change in Get ( TemporaryPath) instead of Get ( DocumentsPath ), but problem persist.
So, i agree with rgordon!
Confirm! Two iPhone with this issue have killed FileMaker Go App and after this procedure works properly! I think was a memory problem with FileMaker Go App.
I will wait for an update... i hope!
Fabiola, you could run a script to see if the PDF is created. If it is, then complete the email. If not, bring up a dialog box to tell the user the email was aborted and they need to restart.
Fabiola is a women name
How can i check if pdf is created? There are filemaker errors that i can use? In FileMaker Guide there aren't error codes for this issue. I'd try insert the file in a continer field and check with native function, but i'm afraid for weight and performance (190kb file).
The app is used by Pony express sometime without experience and i must find a simple solution for not delay the checking procedure.
Sorry about the name. The darn autocorrect made the change. There are a couple of ways to check for the PDF. You could pull the PDF into a global and check to see if the global is empty or you could view the PDF in a web viewer and if the web viewer doesn't display anything you know the PDF doesn't exist. Both of these should run quickly and might be the only way to avoid sending an email without the PDF. Also your users need to know how to fix the problem to be able to send the PDF.
I prefer the first option, but you agree with me that is a bad workaround...
I hope in future release there will a error code, if the PDF engine fails to generate file.
Thanks for support,
I think the work around is great because it solves a problem. What is bad is that you have to use a work around because of a potential bug in FM GO. You might want to report this bug to FileMaker because the more people that report it, the greater chance it gets addressed.
It sounds as though you're creating the PDF and sending it as an attachment in one script step. If that is correct, you might try creating the PDF and sending the email as separate steps. Use a variable to specify the name of the PDF, and then use that variable for the Send Email attachment also.
After saving the PDF - and before sending the email - you can check if any errors are returned for the PDF creation. If the error is 0 (no error), you can probably go ahead and send the email. Otherwise, you can notify the user that the PDF was not generated, and abort (or whatever) the script before sending an email without the attachment. If the user sees the prompt to create the PDF (sounds as though that is not the case in your scenario), you may want to trap separately for error 1 (user cancelled) - usually no need to remind them of that fact.