@yasmine_hajar Thank you for posting this! I have a question that I think would be useful here to address to our users who are not currently on JMP Live but may be experienced JMP users interested in harnessing the power of JMP more seamlessly in a collaboration environment within their company.
You mentioned the options available in your Wafers example, where you simply "Opened in JMP" [you opened the data table that was currently stored in JMP live, added a Profiler report with maximized desirability, and then uploaded the new report you created back to JMP Live. Specifically, you chose "Use JMP Live data table":
Can you describe what happens with the instance of this data table that's currently opened in your JMP session (outside of JMP Live). Based on these options, am I correct in presuming that once you open a table in JMP that's stored on JMP Live, the instance of that opened table is effectively its own instance (i.e. jmp data table version, stored locally on your machine), and is therefore, not connected to JMP Live?)
What about for the situation where you have the Wafters data table stored on your AWS server?
you are correct. The local copy of a data table is not connected to the JMP Live data table. We know which table you downloaded and because of that can make the "Use JMP Live data table" the default. But any kind you changes you made will not automatically be reflected on JMP Live. If you made changes locally you need to update the data on JMP Live through the Publish process.