Skip to content
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

Unique Identifier for Matrix #1167

Open
my2ter opened this issue Jul 6, 2022 · 1 comment
Open

Unique Identifier for Matrix #1167

my2ter opened this issue Jul 6, 2022 · 1 comment

Comments

@my2ter
Copy link

my2ter commented Jul 6, 2022

Based on your comment @brandonkelly #463 (comment)

This happens because Feed Me doesn’t have a way of matching your feed’s blocks with existing entry blocks, so it will always just delete the current entry blocks and recreate them with whatever’s in the feed. [....] We are considering adding a Unique Identifier setting for Matrix fields within the feed settings, which would give you a way of matching incoming blocks with existing ones.

Any progress on this, please?

Also I don't think it should be limited to Matrix field only, a Table / SuperTable should allow to be updated without losing data.

Cheers

@yoannisj
Copy link

@my2ter , I recently landed on related issue #1537 where brandon says the plan is to allow importing entires nested inside Matrix fields via a separate and dedicated feed-me feed.

That said, we’re going to look into making it possible to import nested entries directly via their own import job, via new “Field” and “Owner Element” entry import settings. That way you’ll be able to match incoming nested entry data against existing entries, and update them if they already exist, like any other entry import.

Until then, the recommended solution to import data into multi-site Matrix fields is to change the field's propagation method to "Only save entries to the site they were created in".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants