go to post John Murray · Mar 11, 2016 One caveat about transferring globals between namespaces / instances using XML format is that by default when you load the XML into the target namespace the global(s) in your XML file will be pre-killed. In other words, it's a "replace" operation rather than a "merge" one. This may be exactly what you want in many situations, but if you've been used to using other utilities to export and import globals then it's different.To override this behaviour, add the "/mergeglobal=1" qualifier during your import, for example as the second argument (qspec) to $system.OBJ.Load(), which is of course the Load classmethod of %SYSTEM.OBJ.See more qualifier documentation here.
go to post John Murray · Mar 10, 2016 Thanks Dmitry. That worked, upgrading me from 1.0.107 to 1.0.112
go to post John Murray · Mar 10, 2016 Hermain, I think yours predates the point where ISC implemented the ability to update Atelier from within Atelier. I suggest you download the latest kit and install that. Thereafter you ought to be able to update from within. But bear in mind I'm not an ISC person, so my advice might be incorrect.
go to post John Murray · Mar 10, 2016 Thanks for sharing this detailed information Jamie. I noticed that the headers have links to a wiki on GitHub, but they're unreachable to me and presumably to other non-ISC folk.
go to post John Murray · Mar 10, 2016 Was that repository URL pre-populated in your Atelier?Maybe the response Dmitry gave to this post I created in the Atelier community will help you.
go to post John Murray · Mar 9, 2016 Tiago,Do you mean that when you are writing output from the server (e.g. from a source control class) you want to be able to control the colour of that text? I have never discovered a way of doing that, but let's see if anyone at ISC knows of an undocumented feature there.
go to post John Murray · Mar 9, 2016 I can confirm that the 64bit Windows Ensemble download link is working for me.
go to post John Murray · Mar 9, 2016 That worked. I guess the Developer Community application ought to do a better job with content expiration or something in order to make sure we see the correct images.
go to post John Murray · Mar 9, 2016 Nicki, did you paste the wrong thing as your second image? Under the title "studio:" I'm seeing an Atelier "Create a New Project" dialog screenshot.
go to post John Murray · Mar 9, 2016 Existing users of our Deltanji source code management tool, which runs natively inside Caché / Ensemble / HealthShare, may want to start using Atelier without having first to re-engineer their source control. I foresee a need for an Atelier user to be able to interact with a Deltanji dialog and then trigger a server-side action.
go to post John Murray · Mar 8, 2016 While not directly (yet) addressing Jenny's specific Ensemble HL7 interface scenario, discussions on the "Development teams and namespaces" thread may be of interest.
go to post John Murray · Mar 8, 2016 Certainly looks strange that you can browse namespaces on the Server Explorer tab but the new project wizard says it can't find any. I don't see your symptoms on mine, but I'm connecting to a Windows instance of 2016.2. My Atelier "About" box shows version 1.0.107. Is yours that version too?
go to post John Murray · Mar 8, 2016 Great article Murray. I'm looking forward to reading subsequent ones.
go to post John Murray · Mar 8, 2016 Bill, please update this post when your blog statement appears at http://blog.intersystems.com/compatibility/Incidentally, is there a way to subscribe so I get email notifications when a new blog posting appears?
go to post John Murray · Mar 8, 2016 In your version of Studio, if you open the File\Open dialog and right-click on a package name in the dialog's list, is the a "Delete" option?
go to post John Murray · Mar 8, 2016 What is the $ZV of the server? USER>w $zv What security roles does the user nicki hold? Either check these using Portal, or connect to a terminal session as nicki and write $roles USER>w $username nicki USER>w $roles ... If you connect to this server using Studio and authenticate as nicki, what namespaces does Studio offer you?
go to post John Murray · Mar 7, 2016 Thanks for spending the time to take us on such an informative backstage tour Ben. A lot of this aligns with what I've seen on the many sites where I've implemented our source code management product for customers.
go to post John Murray · Mar 7, 2016 Interesting question. I expect you're already aware of how we can get the value of an environmental variable thanks to the GetEnviron method of %SYSTEM.Util USER>w $system.Util.GetEnviron("TEMP") C:\WINDOWS\TEMP USER> Maybe someone else knows how you can amend one. But if it's not possible, can you improve readability in your code by concatenating the components of your $ZF argument in several stages into a local variable, then passing that variable as the argument to $ZF ?
go to post John Murray · Mar 6, 2016 Certainly Scott. You can now get the full-size PNG file by clicking on the image.
go to post John Murray · Mar 5, 2016 This is a good question. One of the potential benefits of moving to Eclipse is the increased potential for an ecosystem compared to the Studio days. I think that even if Atelier source isn't opened up to us we will still be able to add stuff around it. But it would certainly be cool if InterSystems released it as open source.
