NOTE: This content was originally presented at the InterSystems Global Summit in 2014, however related topics often come up on the Developer Community so I have decided to turn this into an article for easier reference and discussion. However, much of the content was pulled directly from the presentation slides so the article format resembles that of a PPT deck more than paragraphs.
I have an incorrect InterSystems Server Credentials password stored by the Workstation Keychain in VS Code. VS Code is trying to use this incorrect stored credential to access the server and does not prompt or allow me to input a different password. I do not see any settings associated with the Keychain or resetting those credentials. Does anyone know of the process to delete or replace a stored password here?
As noted in the previous article Native API has some limits. So I did some research on a more Terminal-like interface that provides me with access like a console or the IRIS terminal to allow my $QUERY over a global and other nice commands that are not supported/mapped in NativeAPI for ObjectScript.
I have created a method than evaluates an XML expression using the EvaluateExpression method. I need to replace an element value by other string but I couldn't find the way of doing it.
I'm Trying to create a "Windowing Function" In Cache similar to SQL Server. I'm trying to create a Row Number for every account number (Example Below). I know I can use the %Vid function to create the Row Number but I need the row number to reset with every new account number. In SQL Server it would be Row_Number over (Partition by account number order by account number). and Example of what I am trying to create is below.
I have to do intersystems iris objectscript code vulnerability scan. I tried in synck vulnerabilities but it's not supported for the xml file. Can someone guide me? Anyother tools are there to do this?
I have already installed IRIS 2021.1 locally. While working with docker can I use same local database (C:\InterSystems\IRISHealth\mgr\samples\samples.DAT) by using docker volume?
It has been pointed out to me that one of my applications fails to display all of the contents when displayed on an iPhone or a tablet of smaller res that a desktop screen.
Desktop..
iPhone..
The code does not change between the two views of the same page.
I have created a view to stage some data in a different format and then want to reference that view in a SQL query from a table that filters the data from the view using a property of the table.
Example:
select MsgId, FileName, (select ReportName from custom_view where MsgId = ReportId ) as ReportName from main_table
Is this even possible? When I try this, I get an error table not found for the view?
I have an Ens.StreamContainer which holds XML that was received, and I need to validate that against an XSD schema. The schema is very simple, only looking at the root element and maybe a couple other items to ensure the XML is what we expect before continuing the data flow.
s ok=ftp.Connect(server,user,password,port) s ftp.Timeout = 100
i ok {
s ok=ftp.SetDirectory(directory) i ok { n files,file
s ok=ftp.NameList(directory,.files) i ok { f i=1:1:files.Count() { s file=files.GetAt(i) i (ftp.SetDirectory(file)) { d ftp.SetToParentDirectory() continue } s fname=$p(file,"/",$l(file,"/"))
We have a Cache database in Azure, and want to expose it as an OData source (link).
My first attempt was to use Microsoft's Visual Studio 2017 and Entity Framework to create the data models...but it seems as if EF and Cache don't work together. (I do have those instructions from 2013, but they don't work. (See other post. Best answer seems to be "migrate to IRIS 2019.1.")
One of the many benefits of using Atelier for your ObjectScript development is its integration with a wide range of source control systems. This integration enables you to use modern development workflows which increase collaboration while minimizing the risk inherent to volatile code bases.
Veteran ObjectScript developers can tell you about the workarounds that were needed before they could use source control systems with products like Caché and Ensemble. One of these was to treat the data store itself effectively as a code repository. And so shared development environments became essential for many of our customers to be productive and successful.
For code shops that rely on shared development environments, adopting Atelier might seem too complicated. This article aims to provide a practical example to guide your team towards success with Atelier.