- Issue created by @mortona2k
- 🇫🇷France guignonv
Well, xnttmanager is not quite compatible with v3 yet so it might be one problem. "Language" base fields were introduced in v3 and I have not tested the behavior with xnttmanager... but you did and it seems there are issue. I'll try investigate next week (or the one after...), I put that on my stack.
- 🇺🇸United States mortona2k Seattle
The linked comment says to use:
ID: $.id
However, JSonPath is not a valid option for ID. Only Field name is available when JSONPath is selected as the field mapper.
I'm wondering if this might be a bug or regression in the 3.x dev branch?
- 🇫🇷France guignonv
It's not a bug, it's because things are not stable and the id field "now" needs to be a direct mapping (ie. the name of a source field) for technical reasons (possible data aggregation amongst others). But it was not the case before and it may change again...
- Status changed to Fixed
5 months ago 8:07am 14 August 2024 - 🇫🇷France guignonv
I've changed the field mapping interface and it is possible to use JSONPath for id value mapping now. I'll mark this issue as fixed. Reopen it if you think there is something else to fix.
Automatically closed - issue fixed for 2 weeks with no activity.