検索

Article
· Juin 29 1m de lecture

Depuração de API REST: Situação de Página Não Encontrada

Olá desenvolvedores. Só quero compartilhar com vocês uma descoberta que pode salvar alguns minutos importantes da sua vida como desenvolvedor com o InterSystems IRIS.

Mas!

Deveria funcionar; você implantou a API REST corretamente e tudo está no lugar.

O que poderia dar errado?

O problema, no meu caso, foi que eu escrevi o nome da classe errado, como na imagem abaixo:

 

(Havia um erro de digitação ali. E não houve erros de compilação, nem mensagens no console — nenhum indício do que estava errado.)

Então, se você se deparar com um problema semelhante — uma mensagem de “Not Found” para uma página que “deveria funcionar” — dê uma olhada na sua classe Dispatch. O nome está correto?

E, claro, pergunte para a comunidade. Talvez isso economize alguns minutos preciosos da nossa vida de desenvolvedor.

Saudações!

Discussion (0)1
Connectez-vous ou inscrivez-vous pour continuer
Question
· Juin 29

JSON fields and Class properties - are they case sensitive?

Hi noble devs!

Just building a simple frontend->JSON->IRIS backend story, and figured that IRIS while importing via %JSON.Adaptor wants JSON fields to match property names, meaning even should match the case. Like:

{ name: "John", 

surname: "Doe"}

will have issues while saving the dynamic object to a class Sample.Person with:

Class Sample.Person Extends (%Persistent, %JSON.Adaptor)

{

Property Name: %Sting;
Property Surname: %String;
}

As soon as the case is not the same... 

Is there any setting to fix this?) By fixing I mean I want IRIS to don't care about the case JSON fields, as it doesn't matter from SQL point of view, .e.g., IRIS will not allow two same properties but different case:

Property Name : %String;
Property name: %String;

Thoughts?

15 Comments
Discussion (15)4
Connectez-vous ou inscrivez-vous pour continuer
Article
· Juin 29 1m de lecture

REST API Debug: Page Not Found situation

Hi developers. Just want to share with you a finding that might save you a few important minutes of your developer life with InterSystems IRIS.

But!

It should work; you deployed the REST API correctly, and everything is just in place.

What can go wrong?

The issue in my case was that I misspelled the name of the class, like in this picture:

 

It was a typo there. And there were no compilation errors, no console messages - no evidence of what is wrong. 

So, if you face a similar problem - Not Found message for a page that "just should work" - take a look at the Dispatch class? if the name is accurate?

And of course ask the community. Maybe it will save you a few important minutes of our precious developers' life.

Cheers!

Discussion (0)1
Connectez-vous ou inscrivez-vous pour continuer
Article
· Juin 29 3m de lecture

Retour sur InterSystems Ready 2025

Salut la Communauté !

J’ai eu le plaisir d’être votre reporter sur place pour InterSystems Ready 2025, le plus grand événement de l’année dédié aux développeurs d'InterSystems. Comme toujours, ce sommet mondial a été riche en découvertes, en échanges et en innovations. Cette année encore, la Communauté Francophone s’est brillamment illustrée et a pleinement participé à cette aventure inspirante !

@Dean Andrews, @Irène Mykhailova, @Anastasia Dyubaylo, @Adeline Icard et @Guillaume Rongier:

Dès la journée précédant le sommet, les activités ont battu leur plein : golf à l’aube, ateliers techniques passionnants, et moments conviviaux entre collègues. Même si la chaleur et les 18 trous de golf ont eu raison de certains, pour le reste de la journée l’ambiance était au rendez-vous !

Le sommet a véritablement commencé lors de la réception d’ouverture. C’était un vrai plaisir de retrouver des visages connus et de rencontrer de nouveaux membres de la communauté.

@Iryna Mykhailova, @Johan Jacob, @Lorenzo Scalese, @Adeline Icard, @Guillaume Rongier 

Au fil des sessions, @Guillaume Rongier a animé plusieurs démonstrations techniques sur Python et IRIS, captant l’attention des visiteurs du Tech Exchange

On a également croisé Lorenzo Scalese, Guillaume Rongier et Luc Chatty à divers moments phares, notamment lors des jeux "Ready Games", des sessions sur l'IA, et bien sûr, autour de la fameuse "roue de la fortune" au stand de la Developer Community !

@Lorenzo Scalese, @Dean Andrews , @Derek Gervais 

@Muhammad Waseem, @Guillaume Rongier, @Anastasia Dyubaylo, @Oliver Wilms 

@Anzelem Sanyatwe, @Iryna Mykhailova, Luc Chatty

Et que dire du concert à Universal City Walk avec le groupe Integrity Check ?

Même @Randy Pallotta, le guitariste vedette, a fait quelques apparitions parmi nous après le show !

La dernière matinée fut l’occasion de se dire au revoir, de profiter des dernières présentations. Et bien sûr, la session principale de Ready 2025 : InterSystems Developer Ecosystem – les nouvelles ressources et outils à connaître. @Dean Andrews et @Anastasia Dyubaylo ont présenté un aperçu complet de toutes les nouveautés de l’écosystème Developer Community.

Par la suite, @David Reche a mis à l’épreuve l’attention des participants en animant un quiz Kahoot!

Accueillons chaleureusement les gagnants : @Vishal Pallerla, @Rochael Ribeiro et @Jason Morgan. Félicitations ! Nous espérons que vous profiterez bien de votre récompense !

Tout le monde était heureux :

@Juliana Yamao Modesto, @Derek Gervais, @Rochael Ribeiro, @Iryna Mykhailova, @Katia Neves, @Anastasia Dyubaylo, @Dean Andrews, @Enrico Parisi, @Vishal Pallerla, @Eduard Lebedyuk

Merci à toute l’équipe, et en particulier à @Maureen Flaherty, véritable marraine de cet événement. Chapeau bas pour l’organisation impeccable !

@Maureen Flaherty, @Enrico Parisi, @Iryna Mykhailova

À l’année prochaine pour InterSystems Ready 2026 ! Rumeurs confirmées : le prochain sommet aura lieu en avril à Washington, D.C. Notez la date dans vos calendriers, car on espère y voir encore plus de membres francophones !

La Communauté Francophone InterSystems, c’est vous – et nous avons hâte de vous retrouver à Ready 2026 !

Discussion (0)1
Connectez-vous ou inscrivez-vous pour continuer
Article
· Juin 28 3m de lecture

Analytics Cube Definitions and References

Maybe this is well known but wanted to help share.

 

Consider that you have the following persistent class defintions

An Invoice Class with a property reference to Provider

Class Sample.Invoice Extends (%Persistent, %Populate)
{
Parameter DSTIME = "AUTO";
Property InvoiceNumber As %Integer(MINVAL = 100000) [ Required ];
Property ServiceDate As %Date(MINVAL = "+$h-730") [ Required ];
Index InvoiceNumber On InvoiceNumber;
Property Provider As Sample.Provider [ Required ];
Index Provider On Provider [ Type = bitmap ];
/// Build some invoices, this will firstly create 100 Providers
/// <Example>
/// Set tSC=##class(Sample.Invoice).Build()
/// </example>
ClassMethod Build(pCount As %Integer = 100020, pInit As %Boolean = 0) As %Status
{
    #dim tSC 			As %Status=$$$OK
    #dim eException  	As %Exception.AbstractException
    try {
        If pInit {
            $$$THROWONERROR(tSC,##class(Sample.Provider).%KillExtent())
            $$$THROWONERROR(tSC,##class(Sample.Invoice).%KillExtent())
        }
        $$$THROWONERROR(tSC,##class(Sample.Provider).Populate(100))
        $$$THROWONERROR(tSC,##class(Sample.Invoice).Populate(pCount))
    }
    catch eException {
        Set tSC=eException.AsStatus()
    }
    Quit tSC
}
}

and Provider

Class Sample.Provider Extends (%Persistent, %Populate)
{

Property Name As %String [ Required ];
Property NPI As %Integer(MAXVAL = 9000000000, MINVAL = 100000000) [ Required ];
}

If you call the Build method in Sample.Invoice you can query this with SQL

SELECT
InvoiceNumber,Provider->Name, Provider As ProviderId,ServiceDate
FROM Sample.Invoice

and see

The area this article discusses is deciding how to create a dimension on Provider.

What I have found works well is to following this pattern

What this does is 

1. Define the dimension Unique Id on Provider(which is the Id from Sample.Provider).  This is important because it's entirely possible that there is more than one Provider with the name SMITH,JOHN.  By defining the dimension Level on the property Provider we are saying make the dimension table based on a unique Provider.  If we look in the generated dimension table we see

2. Define a Property for the Level that 

 a. Identifies the Property = Provider.Name

 b. Get value at runtime= Yes

 c. Use as member names = Yes

This has the side effect of defining in the dimension table the following Property declaration

/// Dimension property: Name<br/>
/// Source: Provider.Name
Property Name As %String(COLLATION = "SQLUPPER(113)", MAXLEN = 2000) 
[ Calculated, 
SqlComputeCode = {Set {Name}=##class(Sample.BI.Cube.Invoice.Provider).%FetchName({Provider})}, SqlComputed ];

with the %FetchName method looking like

/// Fetch the current value of %FetchName.<br/>
/// Generated by %DeepSee.Generator:%CreateStarTable.
ClassMethod %FetchName(pKey As %String) As %String
{
 // If we don't a value, show key as this is most likely the NULL substitute
 Set tValue=pKey
 &SQL(SELECT Name INTO :tValue FROM Sample.Provider WHERE %ID = :pKey)
 Quit tValue
}

 

What this means is that when a dimension members are retrieved it will return the Provider Name and not the Provider Id.

Using Analyzer we can see

Why is this important?

  1. If the Provider name changes in Sample.Provider the cube does not have to be rebuilt or synchronized.  If we have 100s of millions of invoices and the Provider names changes we dont want to have to rebuild or synchronize the Invoice cube due to a single Provider name change
  2. The Dimension table for Provider is based on the Provider(id) so this allows us to have more than one provider with the same name in the dimension table/cube.

If instead of defining a Dimension Level Property we define the Level Property= Provider.Name this means when the cube is built or syncrhonized 

  1. the dimension unique index is based on Provider.Name which means all of the providers with the same name get aggregated under the same name
  2. If the Provider.Name changes we are required to rebuild the cube
Discussion (0)1
Connectez-vous ou inscrivez-vous pour continuer