I’m having problems with Pro interpreting fields as Big Integer.
I have a table in SQL Server with a field defined as Decimal(10,0) and the largest number stored in this field is 100.
I have two servers, both have Pro 3.5 installed on them. On one server I have a project with this SQL table added and when I look at the field properties in Pro, the above Decimal field is shown in Pro to be ‘Double’. All good.
However, on the other server, I have a Pro project with the table added and it shows this field to be ‘Big Integer’ which is causing me problems trying to publish a map service.
I just tried copying the table layer from the Pro project on the first server (where it is shown as a Decimal field), and pasting it into the Pro project on the second server, and once added, the field shown as Decimal has magically changed to Big Integer again.
Can anyone please tell me how to overcome this issue? I need Pro to recognise this field as Double so I can publish my service.
Thank you.
Mark.
