Problem with Journal Packager Add-in

[#1]

@brady_brady 

I am having a recent problem using Journal Packager Add-in

I have used it very successfully in the past but now it doesn’t seem to be working – The problem may have coincided with switching to JMP18- not sure

The problem is as follows – The add-in is not “stripping” the file path of the referenced JMP data tables

I attach an example of a journal that has been put through the add-in process to demonstrate – you can see that the script file path remains unaltered and has not been converted to a local file path

I have deleted the add-in and re-installed it but the problem has not been resolved

I am using JMPPro 18.2.2 on a Mac

Many thanks for your help

[#2]

Hello,

I am not sure which version you were using previously, but at some point JMP began prompting users the first time they try to open an "external" (usually, internet) file. Perhaps Dropbox falls into this category and other network files fall into this category.

When I placed your files on my machine, the first time I tried to open big class, I received a warning and had to hit "OK" or some such thing to open the file. I then closed it, and when I opened it again, was not prompted (nor did I expect to be). I then ran the repackager addin without issue.

What happens when you try to do what I describe above, rather than work off of Dropbox to repackage? 

[#3]

Brady - I still have same problem when I try to repackage journal file saved direct to my hard drive.....

[#4]

It could be a file permissions (specifically, lack of write permission) issue. First let us see if the path is correctly being changed.

1) Download and install the Journal Text Sledgehammer addin (link immediately below this point), open your journal, and run the addin. Make sure the journal of interest is selected with the radio button(s). If you have opened the journal after running the Sledgehammer, press the "refresh list" button, then select your journal.

https://marketplace.jmp.com/appdetails/Journal+Text+Sledgehammer

2) Navigate to the "Utilities" tab and press the "Scripts into table" button.

3) Press the "Unify paths" button, select "Use local references" and click OK.

4) Press the "Scripts into table" button again. 

5) Compare the 2 entries in the data tables created in steps 2) and 4) above. How did (or did not) the path change? Also, you can opt for the "pick a folder" or "enter manually" options in step 3, to see what happens to the path. If the path is being detected and changed correctly (it was, for me), the issue is likely to be related to file access permissions.

Cheers,

Brady

[#5 · Accepted solution]

Brady - thanks for your help with this

I upgraded to JMP19 and the problem has gone away

Looks like something was corrupted in my JMP18 software that was affecting the Packager add-in

Anyway - all OK now!

Thanks again