AndreaPahor
7 years agoQrew Cadet
Table key from table-to-table import error
We create an equipment ID field in Table A.
The equipment ID is a formula field that creates a unique number:
List("",[ToText: Job ID],[ToText: Sort Order],[ToText: Record ID + 100M],"3")
The equipment ID field is imported from Table A to Table B via a table-to-table import run as part of an automation.
The equipment ID is the key field in Table B.
While the number displays correctly in Table A, when imported to Table B, the last digit of the number changes - but not consistently.
Example:
Table A - equipment ID: 12250001000179553
Table B - equipment ID: 12250001000179552 (i.e. last digit changed to "2")
This leads to attempted duplicate key fields.
When we try to edit the last digit of the equip ID number in Table B (i.e. try to correct "2" to "3") the edit is not accepted. The number continues to display as 12250001000179552.
It appears that this has only occurred as the number of digits in the equipment ID has incremented from 16 to 17.
The equipment ID is a formula field that creates a unique number:
List("",[ToText: Job ID],[ToText: Sort Order],[ToText: Record ID + 100M],"3")
The equipment ID field is imported from Table A to Table B via a table-to-table import run as part of an automation.
The equipment ID is the key field in Table B.
While the number displays correctly in Table A, when imported to Table B, the last digit of the number changes - but not consistently.
Example:
Table A - equipment ID: 12250001000179553
Table B - equipment ID: 12250001000179552 (i.e. last digit changed to "2")
This leads to attempted duplicate key fields.
When we try to edit the last digit of the equip ID number in Table B (i.e. try to correct "2" to "3") the edit is not accepted. The number continues to display as 12250001000179552.
It appears that this has only occurred as the number of digits in the equipment ID has incremented from 16 to 17.