-
Hi,
I have a form published to "Library_A". A workflow moves the form between "Library_B" and "Library_A".
I'd like to save the form using a button.
I'd like users in B to open the form and save it to Library B using the button.
Likewise, after the form is moved to Library_A, I'd like users ...
-
It's a numeric 28, 9, sorry.. Long day.
-
Thanks for your help, Ernesto. The button is already set to always postback and it is indeed doing it (verified using Fiedler). Is extremely annoying.
-
But if the data type is an int in SQL, you'd need to make sure the value you are submitting has no decimals, right? It looks like everything you've tried thus far has 2 digits after the decimal? Sorry, I have a feeling I'm confused. Feel free to attach screenshots under the Options tab.
-
Sorry the Data type is a simpleType. I believe its int in SQL but it comes across as simpleType in InfoPath. It's all coming across fine and looks great. Its only the calculated value creating a very strange long decimal. That wont adhear to the round function.
-
Its not a data issue, It allows 9 decimals the data comes out of SQL fine. It's in the calc value that InfoPath or rather xpath that for some reason is taking a regular number and making a long decimal value..
Ex:
Sql data = 154.200000000 and 200.290000000
in InfoPath the field data will be fine when we view the xml data(matches ...
-
I don't think you need a condition. You need to be setting the value of the queryField.
-
Sorry, I don't know what else to tell you. I have fired up a quick, sample form. In one textbox (string) I used your same formula (I get 06). In the other textbox I just type in the month number (06).
It works fine. The button is disabled and enabled as I expect. That is, the comparison works correctly.
[quote ...
-
I would suggest checking the button's post back settings. Right click, check the properties. The button should be set to Always postback.
-
Euw - got it - what's the data type in SQL? Can it be changed to allow more decimals?