Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
5.0.0, 5.0.0-j6, 5.0.1, 5.0.1-j6
-
None
-
R5.0.3 Sprint 1
-
-
Description
After a long process of investigation, we discovered that as all our custom field names contain a ":" they won't render as part of an Xporter output. Renaming the custom field and removing the ":" resolved the issue, but is going to cause a problem to us.
Can this be fixed within Xporter?
Attachments
Issue Links
- duplicates
-
XPORTER-1086 Custom fields with a white space in their name inside Javascript are not being resolved
- Closed
- is duplicated by
-
XPORTER-1079 Customs fields that contain ":" are not being processed as expected.
- Closed