[ROW-TCP] Data Cleanup: Migrate Attachments on TCP Submission to TCP Submission Content & Remove field

[ChrispinP]

Now that multiple attachments is now live, we will want to migrate all previous submission attachments to the new object and remove the old attachment field to avoid future confusion.

Overall goal & why it matters: Prevent legacy data from being inaccessible. Prevent staff from having to manually re-attach each historical attachment. What's the risk(s) of not doing this: Maintain old fields, files, and views with user experience not as streamlined. How many records are in scope: 5,815 submission cycle records What we think the best solution is: Use Make API to create content records and move files from cycle record to new content record What we need DEV help with: None needed Write the attachment object locations - how does this map?

[johnclary]

@ChrispinP here's the info we need to give this to a dev:

• source object ID (submissions object)
• destination object ID (attachments object)
• a list of each field ID in the source object and what field ID it should map to in the destination object

[ChrispinP]

source object: tcp_submission (object_3) source field: Attachment old (field_37)

destination object: tcp_submission_content (object_13) destination field: Attachment (field_259) connected field: tcp_submission (field_251)

[johnclary]

@ChrispinP @TracyLinder how soon do y'all need this?

[ChrispinP]

@johnclary There is no rush right now. I created the issue so we dont forget about it :)

[TracyLinder]

Putting this on deck; not a priority for this sprint - just a could do if there's time.

[johnclary]

@amenity @mateoclarke this is some tech debt that we don't want to forget. can we earmark it for a not-too-distance sprint?

[TracyLinder]

This will require resources from the DEV team. @johnclary do you have any comments or notes about this you should add here before your departure?

[amenity]

@TracyLinder - feel free to put this on the Product Sync agenda if you would like to bring it to the dev team.

[TracyLinder]

Update - Ready to Move Forward

@ChrispinP will try discuss this at tomorrow's Dev Syc. @TracyLinder will put it on the agenda for the next product sync. @amenity I don't have the meeting invite; can you please forward it to me?

[johnclary]

@ChrispinP can you add a link to the knack app where these files live?

[ChrispinP]

ROW Portal

Old Attachments field from Submission records

To Submission Content object

[ChrispinP]

I added 2 new fields to the Submission object to check if an old attachment is present and then update a Migrated Status Boolean. The Submission Content object also now has a Migrated Boolean to keep track of the records we successfully migrate. There are 5815 attachments to migrate thus creating 5815 new connected Submission Content records.

Here is the Scene for all the Submission records with historical attachments: https://builder.knack.com/atd/row/pages/scene_168

Did some initial testing to see if I could use a trigger to copy files from the parent records to the child records. It successfully copies but shows the file is not available. Reaching out to Knack to see if this is an intended function.

Otherwise an API function/Autopopulate feature may work but a Script may still be more efficient/effective.

[TracyLinder]

Backlog refinement 8/2/23

@ChrispinP could you please update the issue description with a bit more detail.

• Overall goal & why it matters
• What's the risk(s) of not doing this? Both to the stakeholder & tech debt/maintenance
• How many records are in scope
• What we think the best solution is, and any alternative solutions we've identified
• What we need DEV help with
• Write the attachment object locations - how does this map?

Next Steps:

• Chrispin to update description
• Tracy to bring to product/dev sync

[TracyLinder]

@ChrispinP I meant to discuss this at backlog refinement today 🤦🏼‍♀️ - I'll put it on the agenda for the next refinement meeting.

[KyleErich]

@TracyLinder @ChrispinP Has this been done, or is there something still lingering on this?

[ChrispinP]

This can be done with Make but I would need Team support and Stakeholder backing to do so. Would be minimal cost and require no dev work since I can complete myself.

[KyleErich]

@ChrispinP Sure, might be worth mentioning at today's TCP-CM Upgrade meeting (11am, Nov 12).