Can't see Catalogue items in one service

[Guest Paul Alexander]

Hello

In our Test service there are no catalog items showing, and I get an error (as attached)

I really need to get into these CI's for a demo later....can someone take a look please?

[ArmandoDM]

Hi @Paul Alexander,

it looks like the Catalog is bound to a progressive capture  that does not exists.

Can you double check that the Catalogs are all linked to existing progressive captures please?

Regards

Armando

 

[Guest Paul Alexander]

Hi @ArmandoDM

The problem is that I can't see ANY Catalog Items for this service when there should be 3 or 4 items in there:

 

[ArmandoDM]

Hi @Paul Alexander,

the list of catalogs is loaded as a single operation, so if one catalog fails to load, the whole operation fails and the list is not returned.

I run a test and I cannot replicate the issue. 

The catalogs are stored in the table h_itsm_service_catalogs. Could you check that the property  h_pro_capture is consistent for each Catalogs in your service?  Alternatively, you could set h_pro_capture to null and then set them back through the UI ?

Regards

Armando

[Guest Paul Alexander]

Hi again

I do have a support call open for this at the moment too, so I think it's probably just as well to leave it for now!

However, if it helps, when I look at the h_itsm_service_catalog table and click anything, I get the message: "Unable to edit a record with no Primary key"

I'm not sure if that's relevant or not.....also, ALL of the other services are showing their Catalog Items as expected...it's just the Testing service 

thanks

[Guest Chaz]

@Paul Alexander what has happened is that you've been able to create a Catalog without a Progressive Capture against it, which shouldn't be allowed. In our next update, it won't be possible to make that mistake and the list of catalogs will load without error.

[Guest Paul Alexander]

Hi @Chaz

It's good that I won't be able to do it again...but how do I get back so that I can add new CI's please?

thanks

[Guest]

@Paul Alexander Based on our communication in the support call, it was a case of the calalog item being inadvertently created without a progressive capture. We have put in place some code to prevent catalog items from being saved without a progressive capture so it won't be happening again. 

 

Thanks

Pamela

[Guest Paul Alexander]

All sorted now thanks...luckily it was only a Test service so I've deleted the old one and created a new one.

Must remember to NOT do it again on a 'live' service before the fix comes in to prevent this happening again!