Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
5 subscribers
Views
5008 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Parse Excel to CDT
jegadeeswaran
over 7 years ago
Please advice on below issue :
--> when I do parse excel to cdt of column having number which of 10 digit Ex: 1420660768 in Excel is converted to 1.420661e+09. Please let me know any way to fix this one. I don't want to append "Appostrophe" infront of number as business used case is to create excel from other System DB and Upload it in Appian.
OriginalPostID-239024
Discussion posts and replies are publicly visible
0
phanibabuk
over 7 years ago
Hi,
Could you please see if these articles help you?
forum.appian.com/.../10 digit number converting to
forum.appian.com/.../number showing as exponential
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sally Mason
Appian Employee
over 7 years ago
Are you using tointeger()? Please review
forum.appian.com/.../Casting.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ashman
over 7 years ago
Sally, Actually that column is a text type and when we are parsing the value Ex: 1420660768 is changed to 1.420661e+09
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 7 years ago
I think you would need to modify the plugin to fix this issue. If the cell value is a number the java library used will return it as such even if the column is formatted as text in the Excel spreadsheet. It then runs into Appian's inability to handle large numbers so you get the exponential notation. I have had this issue recently myself but fortunatelty was able to get the source system to prefix the values with a fixed character which I then removed in process.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 7 years ago
I would like to add my experiences here, since I just ran into the same issue. In most of my excel templates I use a hidden sheet that replicates the first sheet where we can control column formatting, as user pasted text may be auto-formatted by Excel. I run macros on save to move values only from the first user-facing sheet to a hidden second sheet with defined formats, the excel import then utilizes sheet #2. Only down side so far is that users have to click the 'Enable Macros' button before saving their file prior to upload. For this notation issue, I modified the macros to add a "^" character to the beginning of the text, which is parsed out in the workflow via expression rule, before saving to the primary CDT. Works great!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel