I want to know if there is a way to manually change Primary to secondary and vice versa?
I need this becasue we backup the two VMs (primary and secondary) and my idea is to make a script to when the primary VM is going to backup with Veeam change to "backup" on the mirror.
I working with ORU messages where I'm only interested in routing the message to an operation where any of the contained OBR:UniversalServiceIdentifier.identifier segments contains certain values.
The problem I'm facing is that the OBRs are nested within a repeating ORCgrp, which is then nested in a repeating PIDgrpgrp (although the source only ever uses a single PIDgrpgrp).
Is there a simple way of achieving this without a massive OR for each possible ORCgrp value?
Rather than doing a PnR I can register documents in the XDS.b Registry and store the data elsewhere, such as in the file system. Upon retrieval, however, how can I fetch it from a non-standard location? For example, a progress note whose body is stored in a SDA3 streamlet?
Surely there is an easy way to invoke a ClassMethod from a DeepSee detail listing line, in a similar way to launching a URL. In this case I need to do a little preprocessing of a request adding a SAML token.
I thought I knew how to do it long ago, but I can't read my faded notes on that old parchment.
I'm looking for a means to dynamically specify and/or limit the data from the source that goes into a cube at build time.
I have a single data class that defines my source, and as the data within this table/collection grows/changes over time, I would like to be able to control which records actually make it into the indexed cube, but I'm having a hard time (short of defining a stored procedure to use instead of the extent query) for populating my cube indexes.
I'm new to the Intersystems development world and I've been trying to figure out how to make a REST API using ObjectScript. I found a tutorial that I've been following that has been great and I'm trying to translate what I've learned to live data.
DeadJobAlert: Job 'X478915' for config item 'Business Service' was marked as 'dead' under ghost Id 'sys:ZX478915_6117'
This is the error message I get, but can you advice how can I start debugging this? I look at the jobs and I just see "dead" I cant see any information on the message itself.
I am trying to add pdfbox-2.0.18.jar file into Ensemble and getting below error but with pdfbox-1.x it's working fine. So can anybody please assist me to do fix below issue as showing in screen shot.
I am going to develop a ASP .NET Core Application. In that Hos can use IRIS Entity Framework. I searched but I couldn’t find IRIS Entity Framework for .Net Core . Please kindly help me to overcome this issue.
Hi,
I have installed IRIS community version in my laptop which has Windows 10 OS, also I am already using Healthshare (Cache for Windows (x86-64) 2017.2.1 (Build 801_3_18178U)) in the same laptop. I tried to import objectscript package manager XML file which is downloaded from https://pm.community.intersystems.com/packages/zpm/latest/installer .
I am getting below output which installation failed. Please help to fix this. Thanks in advance
I have Microsoft Visual Studio Community 2019 installed and tried to setup the entity framework as per Using Entity Framework with InterSystems IRIS Data Platform (https://learning.intersystems.com/course/view.php?id=1046) tutorial but I can't see the ISC data source in MS Visual Studio's Data source section. Does this mean that MS VS Community 2019 is not supported with the Entity Frmawork?
Now I want to return a large amount of data to the front end. The string length has reached 40000 +, and the returned data needs to be encrypted by AES + Base64. I can convert the string into a stream. AES can use the AESCBCEncryptStream method to encrypt, but Base64 has no stream method。Anyone who get the solution would you kindly share the solution please。
I've setup an operation that pulls text from an MDM message and uses it to generate a csv file. I'm having issues as our vendor is sending the file with a carriage return (as shown below) to signify the next line but Healthshare is recognising this as a new segment which causes an error.