Matt L.

Here are the modifications I made: For the Service class <class id="Service" _delta="must_exist"> <fields> <field id="isDefault" _delta="define" xsi:type="AttributeEnum"> <sql>is_default</sql> <is_null_allowed>false</is_null_allowed> <default_value>false</default_value> <values> <value id="true">true</value> <value id="false">false</value> </values> </field> </fields> </class> For the ServiceFamily scope SELECT `sf` FROM ServiceFamily AS `sf` JOIN Service AS `s` ON `s`.servicefamily_id = `sf`.id...

Ok I'll try that. Result in a dozen of minutes.

Hello Molkobain, Indeed, debugger seem to point that this issue is occurring while the page is processing the service level. The configuration of the service class was also edited accordingly to what we did on ServiceFamily.

Yes I can ! Basically, DefaultService is just a child class of Service.

Up ? ¯\_(ツ)_/¯

Do you have any update on this issue ?

Due to a data sync between itop and our organization's system, I can't define a top level organization for all organizations. Futhermore, we wanted to detach this DefaultService class of the contract class to be perfectly acurate on the data logic. Concerning the filter on both UserRequest and Incident classes, we added the union query like we did on the portal redefinition. This doesn't seem to be a problem on the normal mode where default services can be applied.