Add an Asset Status

[simonclarke69]

Hi

I would like to add an asset status of 'unserviceable' which is not in the dropdown

Is there an easy process for this somewhere please

Simon

[mfranz · Accepted solution]

Hi Simon,

There is no out-of-the-box process for this. While you can add a new status to the AssetStatus table, the asset status does have an impact on linked devices and I'm not sure how a new status will behave in this regard. 

Instead, the "Retirement reason" field might be easier to customize and use.

Values are stored in the EndOfLifeReason table. Here is an example:

INSERT INTO ComplianceResourceString (ResourceString)
	VALUES ('EndOfLifeReason.Unservicable')
INSERT INTO ResourceStringCultureType (ResourceString, CultureType, ResourceValue)
	VALUES ('EndOfLifeReason.Unservicable', 'de-DE', 'betriebsunfähig'), ('EndOfLifeReason.Unservicable', 'en-US', 'Unserviceable')
INSERT INTO EndOfLifeReason (ResourceName, DefaultValue)
	VALUES ('EndOfLifeReason.Unservicable', 'Unservicable')

Downside is, that this field is only available when the AssetStatus is set to Disposed or Retired. Of course, you can also go with a custom field,  e.g. a checkbox.

[mfranz · Accepted solution]

Hi Simon,

There is no out-of-the-box process for this. While you can add a new status to the AssetStatus table, the asset status does have an impact on linked devices and I'm not sure how a new status will behave in this regard. 

Instead, the "Retirement reason" field might be easier to customize and use.

Values are stored in the EndOfLifeReason table. Here is an example:

INSERT INTO ComplianceResourceString (ResourceString)
	VALUES ('EndOfLifeReason.Unservicable')
INSERT INTO ResourceStringCultureType (ResourceString, CultureType, ResourceValue)
	VALUES ('EndOfLifeReason.Unservicable', 'de-DE', 'betriebsunfähig'), ('EndOfLifeReason.Unservicable', 'en-US', 'Unserviceable')
INSERT INTO EndOfLifeReason (ResourceName, DefaultValue)
	VALUES ('EndOfLifeReason.Unservicable', 'Unservicable')

Downside is, that this field is only available when the AssetStatus is set to Disposed or Retired. Of course, you can also go with a custom field,  e.g. a checkbox.

[simonclarke69]

Thank you , that helps me out with my request. 😀

[simonclarke69]

Hi , just looking in the books on how to edit a drop down , how do I access the tables please ? Manual says use SQL studio ? Where are the xmls or is that a bit risky ? Thank you

[mfranz · Accepted solution]

Hi Simon,

Fields like Retirement Reason are based on a table. They can be changed by adding new entries or removing existing one. As mentioned before, some risks and limitations do exist.

Custom drop-down-type fields are defined using a xml-like structure, but they are normally managed by existing Stored Procedures.

To do any of this, you'll need a SQL Client, of which SQL Server Management Studio is one. And you will need sufficient rights on the database server & databases. And maybe a hole in a firewall.

Yes, there's the risk of "damaging" your FNMS implementation and/or losing data. I would advise testing any changes in a dedicated test environment first. Alternatively, get some experienced consultant to develop and test your use case for you.

BR,

Markward