Unable to add Campaign Conditions when using a campaign which targets a custom ARL
When you use a custom ARL in App Broker for a reclamation campaign, you see the following error when attempting to add or save campaign conditions. This issue occurs because custom ARL values are longer than standard ARLs, and the database column that stores this value is not large enough.
Example of error:
The FlexeraID_FK column in the WD_CampaignConditions table is set to a size of 50 by default. This may not be sufficient if your custom ARL value is larger.
To resolve this issue, increase the size of the column so it can store the full ARL value.
- Connect to your App Broker database.
- Locate the
WD_CampaignConditionstable. - Increase the size of the
FlexeraID_FKcolumn by running the following SQL query:
ALTER TABLE [dbo].[WD_CampaignConditions]
ALTER COLUMN [FlexeraID_FK] VARCHAR(255) NOT NULL- Save the changes to the database.
- Return to App Broker and try adding the campaign condition again.
NOTE: This issue is expected to be fixed in a future App Broker release. Earlier versions may still experience this limitation.
After increasing the column size, App Broker can store custom ARL values correctly, and you should be able to add and save campaign conditions without errors.
