You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a DSE and I'm still seeing tickets about this issue (#45). Even though it's in the docs (as seen in the last response), would it be more clear if it were indicated on the extensions page? It says "Export Format: JSON file (*.json)" but it could mention that exports are in ndjson format.
Multiple customers have tried to export and then import immediately to another tenant.
Let me know if I should continue on issue #45's thread instead.
The text was updated successfully, but these errors were encountered:
Honestly, I find it rather incredible that the export format is not compatible with the expected import format. Surely, the nr. one usecase for this extension is to migrate users between tenants?
I can partially understand the argument about filesize, but not every customer has thousands and thousands of users. It should, at the very least indicate that the export format is indeed not JSON, and not compatible with the import format.
Better yet, let us pick a format compatible with importing, telling the customer to transform the file after downloading with some third party library is downright silly in my view.
The whole process of migrating users from one tenant to another, including the passwords, should be completely overhauled in either case, this is so much harder than it needs to be :)
I'm a DSE and I'm still seeing tickets about this issue (#45). Even though it's in the docs (as seen in the last response), would it be more clear if it were indicated on the extensions page? It says "Export Format: JSON file (*.json)" but it could mention that exports are in ndjson format.
Multiple customers have tried to export and then import immediately to another tenant.
Let me know if I should continue on issue #45's thread instead.
The text was updated successfully, but these errors were encountered: