Open axelstudios opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
@axelstudios / @kflemin -- this is a problem for the City of Berkeley because they have 2 custom fields that they edit and that causes the duplicate data to be imported every time they update their ESPM data.
This has caused them to have to edit the ESPM data file outside SEED and only include data that has changed, which is definitely less than ideal.
Can we bump up the status of this so it gets fixed sooner rather than later ? Thanks !!
https://github.com/SEED-platform/seed/pull/4687 heres a necessary first step
Ammon from the City of Berkeley is happy to demo the issue they are having if that would be useful.
Is your feature request related to a problem? Please describe. Importing data from ESPM, and then adding custom data within SEED (like Salesforce IDs) via manual edits will cause the record to be an in-exact match for every future import rather than an ignored duplicate.
Describe the solution you'd like The Column Settings page should have an additional column with a checkbox to allow specific columns to be excluded from hashing. That way the
hash_object
can be identical to future ESPM imports, even if changes were made in SEED to excluded columns.