go to post Ben Spead · Apr 16 From your initial screenshot: Perhaps you need to be on the 'filerodev2023' Instance, rather than the 'IRIS' instance and you show above on your HOME4 node?
go to post Ben Spead · Apr 16 in the screenshot above you are trying to run the class in the FILERO Namespace. Did you try running that command in FILEROIRIS?
go to post Ben Spead · Apr 15 @Alexandra Mirzac - welcome to the Community :) I would suggest the following: 1) Make sure you have saved and compiled your class, and that it returned with no errors. 2) Make sure when you are testing in Terminal you are connected to the correct Instance and the correct Namespace 3) Double-check spelling and case in your Terminal command compared to your compiled classname Please try those things out and let us know if that moves you forward.
go to post Ben Spead · Apr 9 Nice! Thank you for taking the time to figure this out and write it up! I am sure it will be usable by others in the D.C. :)
go to post Ben Spead · Apr 5 I don't have access to an active HS environment at the moment, but from testing the last part of your query, it looks correct to me. You are saying with the query that has the literal timestamp you get results, but with the 2nd query which targets the prior 2 hours you are getting no results? are you sure that there are records in that time window to fetch? What happens if you change it to a 24 hour window (-24)?
go to post Ben Spead · Apr 5 I would suggest someone open an Issue in the GitHub project to formally request this - https://github.com/intersystems-community/vscode-objectscript/issues
go to post Ben Spead · Apr 4 Can you explain what you mean by this? "it only leaves me specifying the exact time" It makes it sound like you are using a UI of some sort? Assuming that is the case, you should be able to access the records directly from the underlying table using SQL. If you tell us specifically what table you're trying to look at we may be able to be more specific in a recommendation.
go to post Ben Spead · Apr 3 If you go to the class documentation for the %SYS Namespace, are you able to see the Common class? If not, then you may need to reinstall Ensemble in order to get it back. Glad to hear that you were able to get to the root of why you couldn't see the other classes!
go to post Ben Spead · Apr 3 These classes are still in your 2018.1 instance (if they were not you would not be able to log into the System Management Portal), however, the Security.* package only exists in the %SYS Namespace (as it is not a % package it isn't projected to other namespaces). See: https://docs.intersystems.com/ens201817/csp/documatic/%25CSP.Documatic.c... It may have been that you used package mappings to make the Security.* classes available in your application namespace, or that they were mapped by the product (I don't remember - 2014 is 10 years old at this point ;) ). However, best practice today is to change to temporarily change to the %SYS Namespace in your code if you ever need to call the Security.* package. There are privileged calls in there which you typically don't want directly accessible within your application namespace.
go to post Ben Spead · Apr 2 @Scott Roth - there was an issue found with the HSHC 2024.1 kit so it was pulled down and a corrected kit should be available in the near future. So sorry for the inconvenience.
go to post Ben Spead · Apr 2 Thanks - that is what I expected. I think that the older git source control hooks will likely end up being frustrating for you working in that mode. Check out Deltanji, or we will see if there is any chance of git-source-control working for you.
go to post Ben Spead · Apr 2 thank you for clarifying. we'll see what Pravin and Tim say about git-source-control on Caché
go to post Ben Spead · Apr 2 @Token Ibragimov - is your intention to have only a single developer working on this Linux system, or will many developers be making changes? The reason that I ask is that while there have historically been a number of Caché git source control hooks which have been created and discussed on this community (a search here will find several examples), they have all assumed the normal git way of working which is a single developer per environment. This has caused challenges with the typical way of developing on InterSystems products, which is many developers against a single instance. This is why my team created git-source-control, in order to make git available in a way that works more seamlessly with our products. If you are going to be stuck on Caché for a while, you may want to consider other source control options which are designed to work natively with the platform, like Deltanji (https://georgejames.com/deltanji/). Let's see what Pravin and/or Tim think about git-source-control working against Caché 2017.1.
go to post Ben Spead · Apr 2 @Timothy Leavitt / @Pravin Barton - can you please weigh in on whether it is possible to run git-source-control on Caché 2017.1? I know the atelier APIs are present in that version (in at least an early iteration) but are there other things missing which would prevent it from working? @Token Ibragimov - curious, do you have a rough timeline as to when you'll be moving to InterSystems IRIS?
