Closed ashbowe closed 6 years ago
Likely caused by wrong formatting of the CSV file used for importing (when Excel assumes number formatting it will scratch any trailing 0's). You should be able to simply correct the faulty reference(s) from the edit view
On Monday, August 28, 2017, ashbowe notifications@github.com wrote:
Hi Timo, another small issue - when the numbers are set at things such as 95.70 they get displayed as 95.7. This means there are then two 95.7 entries as in the UPR numbering you have a 95.7 and a 95.70. It's there a way to resolve this? [image: numbering issue] https://user-images.githubusercontent.com/21161841/29755765-364bd8aa-8bf9-11e7-905a-66a381cb5b9e.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nmrf/sadata/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/AFiu9BoeKEagjGheEWu3DtgKnqqTkNN9ks5schEigaJpZM4PD-oa .
-- [image: dumpark] http://dumpark.com/
Timo Franz | dumpark.com http://dumpark.com timo@dumpark.com T +64 04 381 3725 M +64 022 011 8070 SKYPE tmfrnz Unfold Data Limited, trading as dumpark
You're right as usual - I've been able to make the necessary updates. Thanks!
Re-opening for checking and fixing CSV import file
Caused when opening (double click) and saving CSV file in Excel. To prevent CSV file must be opened via data import:
Updated truncated references on production database https://sadata-production.firebaseapp.com/recommendations
Hi Timo, another small issue - when the numbers are set at things such as 95.70 they get displayed as 95.7. This means there are then two 95.7 entries as in the UPR numbering you have a 95.7 and a 95.70. It's there a way to resolve this?