go to post Evgeny Shvarov · Dec 10 What a milestone! Thanks, everyone, for these remarkable 10 years together!
go to post Evgeny Shvarov · Dec 7 Hi @John Murray! Yes, unfortunately, we removed the option of providing demo hosting from the InterSystems community for now. Hopefully coming back with better proposals.
go to post Evgeny Shvarov · Dec 7 Thahks @Timothy Leavitt ! Looks better with an example, of course. Hope you'll have some time for it in the future.
go to post Evgeny Shvarov · Nov 27 Ideally, if you share the code sample somewhere so devs can reproduce and see what's really going on
go to post Evgeny Shvarov · Nov 26 Perhaps there are no rows that satisfy the dimension conditions? Or maybe there are build constraints? (1000 rows?)
go to post Evgeny Shvarov · Nov 26 Also take a look $CASE - in some cases can be less wordy and more effective.
go to post Evgeny Shvarov · Nov 18 Thanks @John Murray ! It's a good idea. I'm not sure if the Ideas portal allows such functionality, as it turned out that we are not the first enterprise to consider bug reporting functionality via a private channel of communication, but it makes sense to me.
go to post Evgeny Shvarov · Nov 18 Public exposure of critical bugs is not the best way to support the community. On the contrary, it could be a serious threat to thousands of working and important services.
go to post Evgeny Shvarov · Nov 17 Yes. You find a bug and report it privately to InterSystems, avoiding public exposure. I wouldn't name this new service to report bugs as "philosophy" as it is a newly introduced service for developers who encounter bugs. We'll see how it works, and maybe after some time, we can assess if it can be a "philosophy" or a reasonable approach. Let's see.
go to post Evgeny Shvarov · Nov 17 Hi @Dmitry Maslennikov ! Thanks for highlighting that! The point is that bugs can be dangerous, so we have the privilege to know it in advance and address and take care of InterSystems customers. We introduced this service to have a legitimate way to report bugs found by developers while developing with InterSystems products.
go to post Evgeny Shvarov · Nov 16 My bad. It looks like %source lets to refer to properties only, not methods.
go to post Evgeny Shvarov · Nov 16 Could you please elaborate? There are no scripts. The response I'm getting in Postman is "1", so it is $$$OK. And no evidence of do ##class(%CSP.Utils).DisplayAllObjects() output.
go to post Evgeny Shvarov · Nov 11 Or just add a method in a cube class that does what you want and call it via: %cube.YourMethod(%source.%Id())
go to post Evgeny Shvarov · Nov 11 you can go for: $property(%source.%PackageName()_"."_%source.%ClassName(),"client_name")
go to post Evgeny Shvarov · Nov 10 But I must say Postman seems as a great tool to debug REST API in IRIS, even while debugging local stuff. And it can build collections on the fly on open-api spec provided - very convenient!
go to post Evgeny Shvarov · Nov 10 Hi @Eduard Lebedyuk ! Unfortunately, this approach is not working (at least for me) while using ^%REST approach and disp->impl implementation classes schema: If I put this into the impl classmethod, the only thing I'm getting back in Postman is 1:
go to post Evgeny Shvarov · Nov 10 Yes. The initial idea for intersystemsdc was to avoid waiting on the Docker build process to install IPM and other syntax sugar and good stuff from OEX. So, maybe we don't need intersystemsdc now very much to always get along with official containers set.
go to post Evgeny Shvarov · Nov 9 It is also possible to install Python packages along with IPM via requirements.txt entry. In case it helps anyhow.
