AnsweredAssumed Answered

Export Records FileMaker Pro : lost in translation

Question asked by planteg on Nov 23, 2018
Latest reply on Nov 23, 2018 by Cécile

Like • Show 0 Likes0
Comment • 6

Hi,

I am currently rebuilding a system, which means consolidating tables from many files in a unique file. I use extensively Export Records... with type set as FileMaker Pro Advanced. So I export from a file in the actual system and then import in a new file.

Thing is I realized that during the process I loose fields definitions : a field that was set to calculation becomes a field of the type set for the calculation and a field that was set with auto-enter loose all the auto-enter parameters.

Is this the normal behavior for Export Records in FileMaker Pro Advanced format ? This was not what I expected. What a chore having to repair this. I work with FMPA 17.0.2.205.

Many thanks

comment Nov 23, 2018 6:27 AM

Correct Answer

Is this the normal behavior for Export Records in FileMaker Pro Advanced format ?

Yes. Export means export data. To preserve the schema, you can import from the original file, and select [New Table] as the target.

See the reply in context

No one else had this question

Outcomes

comment Nov 23, 2018 6:27 AM

Is this the normal behavior for Export Records in FileMaker Pro Advanced format ?

Yes. Export means export data. To preserve the schema, you can import from the original file, and select [New Table] as the target.

2 people found this helpful

Actions

planteg @ comment on Nov 23, 2018 6:38 AM

Oh I see .

I now have to find a way to repair this mess without taking too much time.

Actions

Cécile @ planteg on Nov 23, 2018 7:42 AM

Curious here. When you import in the new file, you import the data (from the old file calculated fields) into fields that are defined as calculated field as well or not?

Actions

Cécile @ comment on Nov 23, 2018 7:46 AM

When you do an export and import with Excel, does that do the same? I used to do tons of these and do not recall having encountered such behaviour?

Actions

planteg @ Cécile on Nov 23, 2018 7:46 AM

Exactly. If for example a calculation field is set to return a number, the field is changed to number and set to the value.

Actions

Cécile @ planteg on Nov 23, 2018 7:48 AM

Well for calculation fields, fixing it is quick; just changing the type will put the calculation back. However for autoenter fields, that's a bummer....

Actions

6 Replies

comment Nov 23, 2018 6:27 AM
Unmark Correct
Correct Answer
Is this the normal behavior for Export Records in FileMaker Pro Advanced format ?
Yes. Export means export data. To preserve the schema, you can import from the original file, and select [New Table] as the target.
2 people found this helpful
Like • Show 0 Likes0
Actions
planteg @ comment on Nov 23, 2018 6:38 AM
Mark Correct
Correct Answer
Oh I see .

I now have to find a way to repair this mess without taking too much time.
Like • Show 0 Likes0
Actions
Cécile @ planteg on Nov 23, 2018 7:42 AM
Mark Correct
Correct Answer
Curious here. When you import in the new file, you import the data (from the old file calculated fields) into fields that are defined as calculated field as well or not?
Like • Show 0 Likes0
Actions
Cécile @ comment on Nov 23, 2018 7:46 AM
Mark Correct
Correct Answer
When you do an export and import with Excel, does that do the same? I used to do tons of these and do not recall having encountered such behaviour?
Like • Show 0 Likes0
Actions
planteg @ Cécile on Nov 23, 2018 7:46 AM
Mark Correct
Correct Answer
Exactly. If for example a calculation field is set to return a number, the field is changed to number and set to the value.
Like • Show 0 Likes0
Actions
Cécile @ planteg on Nov 23, 2018 7:48 AM
Mark Correct
Correct Answer
Well for calculation fields, fixing it is quick; just changing the type will put the calculation back. However for autoenter fields, that's a bummer....
Like • Show 0 Likes0
Actions

Export Records FileMaker Pro : lost in translation

Outcomes

Related Content

Recommended Content