Issue Summary

When updating objects using importing, if the object contains a Confluence page attribute, the import fails with "The value provided is invalid". The error persists even if the Confluence page exists and the importing user has permission after upgrading to JSM 5.14.x.

This appears to be due to the fix for: JSDSERVER-14377 - which added the LONG_VALUE column to the AO_8542F1_IFJ_OBJ_ATTR_VAL table. 

Steps to Reproduce

1. Install JSM 5.13.x or below with a Confluence application linked.
2. Configure an import and import some objects.
3. On the imported objects, add some additional attributes like:
   1. Confluence Attribute: Confluence Page
   2. Text attribute: Text
4. On the created objects, link a Confluence page with the Confluence attribute type.
5. Upgrade to JSM 10.x.
6. Run another import to update the same objects with some modified values, like the Text attribute. 

Expected Results

The import will proceed without issues, and UI updates will also function properly.

Actual Results

The following error message will be presented on the UI while importing:

The value provided is invalid 

In the insight_import.log, the following error will be seen:

2025-11-12 11:36:16,581 [insight-InsightImportThreadGroup-1-worker-thread-10] {jira.username=admin2} | Failed to update object: User01 (TEST-1), ObjectTypeId: 1, Attributes: (AttributeTypeId: 33, value(s):[-1(196694)],AttributeTypeId: 2, value(s):[null(User01)],AttributeTypeId: 34, value(s):[null(Valueeee)]), avatar: false with actions: [UPDATE] due to ValidationInsightException: Validation errors were found: rlabs-insight-attribute-33: ErrorMessage{i18nKey='rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.Invalid.data', parameters=[], additionalMessage=null}; 

While updating the object via UI:

On the Assets Schema UI, if a user WITHOUT Confluence permission tries to save one affected object, the following error will happen:

On the Assets Schema UI, if a user WITH Confluence permission attempts to save an affected object, this resolves the issue as the value is transferred to the LONG_VALUE column.

When manually resaving the object, the behavior in the database will be:

Before re-saving the object:

After re-saving the object:

Workaround

• With a user having a Confluence license, manually click ‘Edit’ and save each affected object in the UI. This refreshes the attribute on the database columns and allows future imports to succeed.

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: