Re: Dropdown Table Field Data Artifacts

Method_Adam — Fri, 14 Dec 2012 17:28:52 GMT

Blake,

I was actually able to recreate this with two custom tables. I'll put in a ticket with the team.

- Adam

Dropdown Table Field Data Artifacts

Blake C — Wed, 12 Dec 2012 23:03:28 GMT

I'm looking at table data and notice that for each Dropdown field in a table, there is a corresponding 'dropdown field name_RecordID' field as well. I've known this for a while now...but what I just now discovered is this - Should the referenced dropdown field ever get deleted from it's respective table, thereby severing the link, I noticed the referenced '_RecordID' field still contains the now non-existent record ID. Is there a reason for this or just an oversight? It's not causing any problems from what I can tell, but if anyone ever looks at data or tries to work with data outside Method it could be confusing to have IDs that don't exist populated in tables. It just confused me.

Example (not sure if this helps or not):

Table 2 references SalesOrderLineItem as a Dropdown field (via RecordID). Because of this assocation, Table 2 now has a field called SalesOrderLineItem (linked via Dropdown) AND a new field called SalesOrderLineItem_RecordID. Should a SalesOrderLineItem row be deleted that happens to be referenced by Table 2, the data in the field named Table2.SalesOrderLineItem_RecordID will still show the record ID that no longer exists. However, the field named Table2.SalesOrderLineItem that previously held the (now non-existent) ID is appropriately empty.

Make sense?

Method:Classic General Q&A

Re: Dropdown Table Field Data Artifacts

Dropdown Table Field Data Artifacts