-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update by System ID #19
Comments
@nilshoerrmann planning on working on this / something similar next week. When you say update by System ID, are you passing the Symphony System ID or an arbitrary ID from another system which is stored in symphony? |
The Symphony system id. Using another id is already possible as it will be stored in a field as any other import value and can be used to determine entry identity. |
Ah right, will try to figure this out next week. Ideally I want to see if it's possible to create an import which pre-sets the entry ID, so I'm sure if I figure that out the update should be relatively straight forward. |
@nilshoerrmann & @brendo currently working on this - I think I should have a PR by end of day tomorrow for testing. Just to confirm some minor things. To each section field chooser I'm adding a new "Entry ID" Element, the user has to make sure this is an integer (otherwise no other constraints) as long as I use Other than that will be conducting some further testing to ensure that updates also work properly. |
@nilshoerrmann if you have some time can you check if #40 would work for you? Or do you require additional options? |
Cool. I'll have a look soon. |
As already described in #18, we'd like to update entries using an external data source. This source features existing system ids but there is no simple way to update entries based on their system id.
While it's logical that you don't import system ids when creating new entries (they are of course created by the system on save), it makes sense to match entries by system id when updating existing entries.
The text was updated successfully, but these errors were encountered: