Acting as an SME was a fantastic experience.   Myself and my paired expert were able to really dive into some interesting avenues of discussion, combining our different approaches and experiences, and distilling them down to a common understanding.  It was a truly valuable exercise to expand and reinforce my knowledge of the great products we offer

I think it's the indention of the ClassMethod line. If you remove the leading space before it, then the Language Server should be happier about parsing the method

We have used Continous Integration to help with this.  Our Jenkins build will pull the source, compile it, zip it, and attach back to the Jenkins job.  On success, a secondary job sends this zip to the server, unpacks it, and updates the symlink for the web folder to the new one.  This way we only move source files, and we are not having to worry about build processes on a production environment

Yes, if you set up a response and request programatically as Oliver Thompson said, then you can just call the ClassMethods rather than going through HTTP to Rest.   

The original article is here:  https://community.intersystems.com/post/creating-iris-cross-functional-app  The recorded demo is slightly different for a few reasons, and <spoilers> the final demo does not work, but only because of time constraints and a slight typo in code.  See if you can spot it!

JSON_Table got a deep dive in the context of the Document DB functionality.  @Stefan Wittmann presented an excellent session about this at last year's Global Summit

https://www.youtube.com/embed/T7RzkugC7QQ
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

this looks ok.  Maybe try 

zw myobj

before entering the loop, just to make sure that the file stream has linked up ok?

It's probably your date fields - typically SQL in code will run in Logical mode, not ODBC mode

Try explictly setting the SelectMode to ODBC and see if that helps?

https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...

It sounds like $SYSTEM.Version.Format() might get you what you need?

https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...

TRC>w $SYSTEM.Version.Format(5)
2024.1 (Build 262U)

But 345678 is not of Type NPI, its an Employee_Number in your output above.  Restricting the subquery to NPI will return nothing for that number.   If you change the subquery to the correct Type restriction,  i would expect this to work

I am very confused about what the inputs are, and what the desired output is, but in that case a subquery would be needed

SELECT *                      
FROM PhysTable                        
WHERE ProviderName = 'DOE, JOE' AND Type = 'NPI' 
AND ProvId =(
             Select ProvId 
             from PhysTable 
             where ProviderName = 'DOE,JOE' 
              AND Type='EMPLOYEE NUMBER' 
              and IdentityId = 345678
            )

Not sure I am quite understanding the ask, but I think you want something like

SELECT *                        
FROM PhysTable                        
WHERE ProviderName = 'DOE, JOE' AND Type = 'NPI' AND ProvId =8252

This looks fantastic,  Installing it now!

Just a note for reference in future.  The DynamicAbstractObject functionality was fully implemented in Caché 2016.2 and up (there was a version in 2016.1, but the syntax is different).   If you are on a higher version that this, using it is generally preferable to the ZENProxyObject version