Hi,
I am assuming, you're using FNMS on-premises. And I further assume you're talking about the EOL fields in the SoftwareTitle table, like SupportedUntil, ExtendedSupportUntil etc.
You can add missing columns, but it's probably not supported and is quite some work. If you have a test environment, I suggest you test it there first. Here are the steps I used for "Supported until":
1. You'll need to add a ComplianceResourceString because the other steps will need to refer to something. You can use whatever name you like, but I would stick to the existing schema.
INSERT INTO ComplianceResourceString
VALUES ('ComplianceSearchTypeColumn.SupportedUntil')
2. You'll need to to add one or more translations (ResourceStringCultureType) for your new report column. I just did an English one, feel free to add more languages as needed.
INSERT INTO ResourceStringCultureType
VALUES ('ComplianceSearchTypeColumn.SupportedUntil', 'en-US', 'Supported until')
3. You'll need to add the actual ComplianceSearchTypeColumn.
INSERT INTO ComplianceSearchTypeColumn (
ColumnName
,ColumnNameResourceName
,QuerySetup
,FromTable
,SelectName
,JoinClause
,WhereClause
,SelectOptionsSQL
,FilterGroupType
,DefaultFilterType
,ComplianceSearchTypeID
,RequiresSearchTypeID
,Mandatory
,PrimaryKey
,SelectByDefault
,IsCustom
,LinkAction
,LinkController
,LinkIndicateOrigin
,LinkFragmentField
,IsMultiEditEnabled
,MultiEditConditionField
)
VALUES (
'SoftwareTitle.SupportedUntil'
,'ComplianceSearchTypeColumn.SupportedUntil'
,NULL
,NULL
,'SoftwareTitle.SupportedUntil'
,NULL
,'SoftwareTitle.SupportedUntil'
,NULL
,4 -- Date
,4
,8 -- SoftwareTitle
,NULL
,0
,0
,0
,0
,NULL
,NULL
,0
,NULL
,0
,NULL
)
You'll need to repeat the same for the other EOL columns. This is a rather simple example, no joins are made to other tables. While the date filter type is cumbersome in the standard filter (equals), the advanced filter (greater than, less than) makes it useful.
Best regards,
Markward
