-
Do you suppose leap year is coming into play here at all? If you really just want to add years, let me know - you could do that with a substring formula, because incrementing the year is simple. XML dates are stored in yyyy-MM-dd format, so you can use substring-before to get just the year and increment it.... something like: ...
-
I can't imagine an Excel Calc. services error would have anything to do with the form's failure to submit to the list. If you drag your CAML XML onto the form when you submit, does all the data look ok? If you try to manually create a list item with the same data, do you succeed?
-
You'll need to use the addDays() function in InfoPath. So in your formula editor, click the button for inserting a function, and find the addDays() function. The first parameter is your date field and the second is the number you want to add. So maybe xdDate:AddDays(../my:field8, (../my:field22 * 365))
-
That's right. Sorry, hadn't realized you were working with a list form. Maybe have a field that is multiline (so that you can have unlimited chars) and just concat in the info each time the target changes? Another sample attached.
-
You'll need to add code to your InfoPath form in order to consume the input parameter, if you can't use the web part approach. The code is pretty simple: https://blogs.msdn.microsoft.com/infopath/2007/02/26/passing-data-into-a-form-input-parameters/
But, once you add code to the form, it has to either be admin approved, ...
-
Ok - so is this an on premises SharePoint 2013 server? If so, try submitting your data and then go check the ULS logs to see if they have any info that may help.... I would think if the issue was due to loopback check you'd get an error when the web service data connection executed, however.... Are you submitting data to any date time column ...
-
So - if your InfoPath form is based off a SharePoint List, you can't get around column limits. If your InfoPath form is published to a library, and is not a list form, then you can choose what data is visible in the library when you publish the form by selecting the columns to promote. That means the fields the users don't need to see in ...
-
Oh. I see. I hadn't realized you were saying the form is behaving differently in the browser vs. in the filler. I've never seen that happen w/ a double eval before. When you say "SharePoint view" - you do mean in the form itself in the browser, right? You aren't talking about a promoted property value or anything like that? ...
-
Not to my knowledge - I'm sorry. Is there a way you can pick which fields to promote? Or are they all equally important?
-
It looks right to me. I guess you could always try:
xdMath:Eval(xdMath:Eval(xdXDocument:GetDOM("Workbaskets_US_Assignments")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW[d:US_x0023_ = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:ID]/d:New_x0020_Assignment_2, 'concat(., ...