Home Service Manager Asset Management Feature Requests
We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Put Views and Lists for Asset Management in a separate unsealed management pack

Tony_CollettTony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭
Currently, if you modify any list value or view in Cireson Asset Management, you can save it to a separate unsealed management pack, however when upgrading CAM these modifications get overwritten unless you reimport the MP that stores your custom values. 

With a large system like CAM, it should be easy to upgrade without keeping track of all the custom modifications to ensure they don't get overwritten. 
15 votes

Declined · Last Updated

Sorry, we've done some research around this and the change would be very disruptive to current customers and if you are using separate management packs for your customization then you shouldn't have this issue. Please contact support if you are seeing something overwritten that is outside of the CAM management packs.


  • Options
    Brett_MoffettBrett_Moffett Cireson PACE Super IT Monkey ✭✭✭✭✭
  • Options
    seth_coussensseth_coussens Member Ninja IT Monkey ✭✭✭✭
    We will look into this and once confirmed, determine if this is a bug or a new feature that needs to be implemented. Either way, I agree with you assessment that this shouldn't be an issue.
  • Options
    seth_coussensseth_coussens Member Ninja IT Monkey ✭✭✭✭
    We've tested this and actually do NOT see this happening. When you have a separate management pack that is created because the base MP is sealed, that new unsealed MP actually references the sealed MP, not the other way around. Importing a new CAM mp, as long as it's just a version change should not break this linkage. What you are describing actually sounds like a bug in service manager or your particular environment. This is something you should open a support case for to track down the issue.
Sign In or Register to comment.