You may ask: how to export the file?
There is a special "helper" package "isc dev", once installed via:
zpm "install isc-dev"
and set up then as:
do ##class(dev.code).workdir("/home/irisowner/dev/src")it will allow at any moment to export all the DFI at once into your dev folder with the command:
d ##class(dev.code).export("*.DFI")Hi Ashok!
Yes, you can use IPM to support DFI files.
"Lazy", aka "dirty" way - introduce the following resource:
<Resource Name="*.DFI" />
like here, which will package everything you have in a src/dfi folder. Convenient but not optimal and can introduce problems while working with more than one IRIS BI packages.
in this case resource will import all the 100+ DFIs (pivots, dashboards) into IRIS (via load command) and package/publish then:
Don't ask me, why DFI is an XML in fact.
Neat! Thank you, looks easy and practical! Thank you for sharing!
What a milestone! Thanks, everyone, for these remarkable 10 years together!
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.
Thank you for introducing, @José Pereira ! Will take a look!
Thahks @Timothy Leavitt ! Looks better with an example, of course. Hope you'll have some time for it in the future.
Ideally, if you share the code sample somewhere so devs can reproduce and see what's really going on
Perhaps there are no rows that satisfy the dimension conditions?
Or maybe there are build constraints? (1000 rows?)
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.
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.
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.
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.
My bad. It looks like %source lets to refer to properties only, not methods.
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.
Or just add a method in a cube class that does what you want and call it via:
%cube.YourMethod(%source.%Id())
you can go for:
$property(%source.%PackageName()_"."_%source.%ClassName(),"client_name")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:
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.
It is also possible to install Python packages along with IPM via requirements.txt entry. In case it helps anyhow.
We have 50+ packages on IntegratedML on OEX? wow. @Thomas Dyar
Thanks @Eduard Lebedyuk ! I'll give it a try!
Will it work for POST requests too?
And is it for Postman only? E.g. if I use swagger-ui how could I get this page displayed?
Another one-liner suggested by @Robert Cemper recently:
k ^SPOOL s %io=$I O 2 u 2 ZW %anyvariable c 2 u %ioE.g. if you want to expose the content of %request during REST API method debugging, to write all the contents of %request to ^SPOOL global:
k ^SPOOL s %io=$I O 2 u 2 ZW %request c 2 u %ioand then ZW ^SPOOL in the terminal.
It is a global, again, though... But a very interesting and useful way to convert any write to a device into a global.
Deserves a one liner input!
Thank you, @Robert Cemper !
This works like a charm!
So, in my case, I also wanted to see what's in a stream object that comes into the method (you may ask me how I don't know this, as it is method I coded? ) I don't, as it is a generated one via %^REST):
ClassMethod submitForm(formData As %Stream.Object) As %Stream.Object
{
set formDataObj= {}.%FromJSON(formData.Read())
k ^SPOOL s %io=$I O 2 u 2 do formDataObj.%ToJSON() c 2 u %io
return $$$OKAnd then I do a REST API call and can see data in the terminal with zw ^SPOOL global:
USER>zw ^SPOOL
^SPOOL(1,1)="{""amount"":0,""name"":""John Doe"",""taxid"":""AB123456C"",""nationality"":""british"",""email"":""john.doe@example.com""}"
^SPOOL(1,2147483647)="{67504,40535{2{"Simple and easy! Fantastic, @Robert Cemper !
Thanks, @Robert Cemper !
But here I'm more interested in debugging the REST API implementation method, so it is not very useful in this case, right?
Wow, thanks @David Hockenbroch !
Is it as simple as that? So when we receive a web call, it is all about the %request with the Method and content filled?
This could also be the way to unit-test REST-API methods
Hi Ed @Eduard Lebedyuk !
Where do I see this displayed data by:
do ##class(%CSP.Utils).DisplayAllObjects()
?