Loading...

XML

Word

Printable

Missing denormalizers for
- type: content_type_group, mode: create
- type: user_group, mode: create, update
There is a typing mistake in one of the exceptions: "Content type * filed* needs to have type defined"
The match type location_remote_id is missing for type: content, mode: update
By updating fields in a content fieldTypeIdentifier is mandatory - if we do not change the value it would be possible not to require it
By creating content for a content type which have fields with type ezobjectrelationlist, you have to define destinationContentIds instead of location_remote_ids
By creating content a description value for fields is mandatory, but it is not mandatory in BackOffice
PublicationDate and modificationDate need a string. By converting with ibexa kaliop convert command UNIX int timestamps are taken over
sortField are also taken over with a string e.g. priority. Better to define sortField with a string of the fields name like it is in kaliop, that would improve readability, same for sortOrder option
By creating content, the section needs by section id instead of the section identifier. The same point as the content id instead of the location_remote_id

relates to

IBX-1569 As a Developer, I want to update the user group in the migration process

1.	As a User I want to use section identifier during Content Create in Migrations	Closed	Unassigned
2.	As a User I want passing FieldTypeIdentifier to not be mandatory in Content Update	Closed	Unassigned
3.	As a User I want to use Location's RemoteID for matching in Content Update	Closed	Unassigned
4.	As a User I want "description" to be optional in Content Create	Closed	Unassigned
5.	As a User I want PublicationDate and modificationDate to allow timestamps	Closed	Unassigned
6.	As a User when creating content for a content type with ezobjectrelationlist field, I want to use LocationRemoteID	Closed	Unassigned