Serial number issue

OttoDeploy
1

Hi,

I believe I’ve discovered a bug. When deploying Otto changes the serial numbers in the file being deployed so that the next serial number is set to what it should be in the live file. The issue with this is that in a lot of cases our systems have got the serial numbers defined as “INV0000001” but when Otto updates the next serial value it is updated to be “2” rather than “INV0000002”.

Obviously these days you would use UUIDs instead but, for some of our older systems this limitation can be a bit tricky to work around.

2

Hey Bradley,

Is this during a data migration? OttoFMS does not do the data migration itself and it does no manipulation of the contents of the file during migration, all of that is handled by the FileMaker Data Migration Tool. If there is a bug with how the data is migrated between files we won’t be able to do anything about it. Have you reached out to Claris about this?

-Kyle

3

Hi Kyle,

Thanks for the response! That all makes sense. I’ll raise a ticket with Claris and ask them if there is anything that can be done.

4

It is possible that your field might be of a number type instead of a text type and the DMT is parsing out the number instead of mapping the whole text entry, which may be something for you to check.

-Kyle

5

Hi Kyle,

Good thinking but, I’ve already checked that and it doesn’t appear to be the case. Our fields are set up as Text fields.

I’ve raised a ticket with Claris so, I’ll see what they have to say and update this topic when they get back to me.

Cheers!