go to post Enrico Parisi · Aug 28 it doesn't seem like the Results of the Class Method are coming back correctly 100% of the time. This is VERY strange, I would add a test/check if an error occur testing SQLCODE and %msg after &SQL() to see if/when/why it fails. When using embedded SQL you are not supposed to check/access a returned variable (ExtDisplay in your case) before checking for success/failure via SQLCODE variable. If you need to check if the query found a row, you should check the SQLCODE value, not ExtDisplay value.
go to post Enrico Parisi · Aug 26 Went to the sea or a lake: Hiked/enjoyed nature: Earned points and redeemed a reward on Global Masters 🏆Many rewards...too many to count! 😊 Joined READY 2025 🎉Yep! See first picture in this Discussion 😉 Spent time with family or friends: And, a lot of relaxing!...I definitely needed it!
go to post Enrico Parisi · Aug 26 This is very confusing, I understand editing names for privacy reasons, but you are changing the actual format, not only names. I've never seen "##class(|"NS"|Path.To.Class)" in errors. Can you reproduce the issue with a simple sample code using generic names? This way you can post your code so we can understand what's going on and how to fix/log the problem.
go to post Enrico Parisi · Aug 25 I don't think that ##class(|"NS"|Path.To.Class).ClassMethod() is a valid syntax. I believe the "|NS|" makes it a syntax error.
go to post Enrico Parisi · Aug 25 s %sc=##class(|"NS"|Path.To.Class).ClassMethod(..%p1,%p2) Is this really contained in the error message? Is that your code? To me |"NS"| and ..%p1 look strange.
go to post Enrico Parisi · Aug 25 Try with: <Map Prefix="/v([0-9]{1,2})/news/([^/]*)" Forward="API.Dispatch.news"/>
go to post Enrico Parisi · Aug 22 Try with: <Map Prefix="/v([0-9]{1,2})/news/:id" Forward="API.Dispatch.news"/>
go to post Enrico Parisi · Aug 22 Stream compression is enabled by default since version 2021.2, see release notes: Saving on StorageStream compression – is now on by default for all globals-based stream classes, with no application change required. Existing data remains readable and will be compressed upon the next write. Experiments with real-world data have indicated compression ratios ranging from 30% for short texts to 80% and more for XML and other document types.
go to post Enrico Parisi · Aug 1 Please check the relevant documentation: Executing Stored Procedures I've asked the DC AI chat bot and the answer is worth a look: https://community.intersystems.com/ask-dc-ai?chat_id=1920 Note that using SQL Server ODBC you probably do not need to specify "IOType" in the param array. If you still have problems, get back with a sample code of what you are doing.
go to post Enrico Parisi · Aug 1 Using the Wheel of Names, we've chosen one random lucky winner: 🏆 Random award goes to the idea Do not include table statistics when exporting Production for deployment by @Enrico Parisi 🤣😂🤣😂
go to post Enrico Parisi · Aug 1 If you post an example of the code you are using maybe someone can help you understand the problem.
go to post Enrico Parisi · Jul 4 Never, ever, concatenate parameters to an SQL Query! Fixed for you: Set sqlQuery = "SELECT * FROM %Dictionary.PropertyDefinition WHERE parent = ? ORDER BY SequenceNumber" Set resultSet = ##class(%SQL.Statement).%New() Set status = resultSet.%Prepare(sqlQuery) $$$ThrowOnError(status) Set tResult = resultSet.%Execute(className) While tResult.%Next() { Set Name = tResult.%Get("Name") ... } Back to your initial question, what is your definition of "sorted by Storage"? If you need the ($list) position of properties within the global, then your query does not answer your question.I'm writing this in case other community members read this question/answer.
go to post Enrico Parisi · Jul 1 It takes a lot of imagination and fantasy to understand what you need without an example of (pipe delimited) input and (json) output.😉😊
go to post Enrico Parisi · Jul 1 Set json=##class(%DynamicAbstractObject).%FromJSONFile("c:\temp\scott.json") Set itemIter=json.items.%GetIterator() While itemIter.%GetNext(.key, .item) { Set identifiersIter=item.identifiers.%GetIterator() While identifiersIter.%GetNext(.key, .identifier) { If (identifier.typeDiscriminator="ClassifiedId") && (identifier.type.term."en_US"="Scopus Author ID") { Write "pureId: ",identifier.pureId,! Write "uri: ",identifier.type.uri,! } } } Output: pureId: xxxxxxxx uri: /dk/atira/pure/person/personsources/scopusauthor P.S.: please note that, as posted, the json sample you provide is invalid.
go to post Enrico Parisi · Jul 1 %System/%System/RoutineChange A process generates a %System/%System/RoutineChange event because a routine has been compiled or deleted. When enabled, this event causes a record to be written to the audit log whenever a routine or class is compiled. The Description field of the audit record includes the database directory where the modification took place, what routine or class was modified, and the word “Deleted” if the routine was deleted. This Audit Event is available in IRIS, I have no idea if was available back in 2018.
go to post Enrico Parisi · Jun 30 Yes, pretty sure, that is what is taught in the ISC training courses and what the documentation says: Description ($PROPERTY)Property names are case-sensitive Selecting FieldsField names in a SELECT statement are not case-sensitive. SqlFieldName names and property names are case-sensitive. Rules for Class Member NamesNote that the system preserves the case that you use when you define classes, and you must exactly match the case as given in the class definition. However, two class members cannot have names that differ only in case. For example, the identifiers id1 and ID1 are considered identical for purposes of (uniqueness.)
go to post Enrico Parisi · Jun 30 You probably have a special use case but, in general, I don't think it makes a lot of sense because: Class properties ARE Case-sensitive by its nature (contrary to your statement in Ideas portal) JSON fields ARE Case-sensitive by its nature (as per JSON standard)