-
Completely random? Like - if you re-run the workflow for the same item, with no changes, it will run successfully? Or could it be that in some cases there is a data mismatch?
-
It is possible - query the list to get all items back, sort by ID desc. so that the first item will be the highest number, and add one to it. You need to be aware that if multiple users are querying the list at the same time you have a chance of more than one getting the same number. ...
-
Makes you want to tear your hair out sometimes, right? So - both of these are list forms?
-
So - they can't open in Filler or the browser? Is there an error, or do you have more details on the behavior?
-
I had to check this theory. I turned on versioning in a list, set a column to append, and then edited it a few times to get some history in place. Then I deleted one version of my list item - and that removed the history for the column w/ append for that version. So, yeah, I don't think this can be done (at least not easily...)
-
Hi - my guess would be that the allow append option is not going to let you actually delete any history. I think (since versioning has to be turned on to allow for this) that the "history" is actually pulled from prior versions of the list item and that to actually delete a history item, you'd have to somehow delete that version ...
-
Hi, Rommel - no, it does not. You can add another field to your data source (not displayed on your form) with a default value for this and map that instead.
-
As best as I can determine, this happens when we add formatting to a calculated value - the binding gets added to the view & has to be manually removed. If you need a hand after you finish your calc'd values, just attach the form to another reply & I'll help you fix it up.
-
Hopefully this fixes that up - InfoPath generally seems to do this when formatting is set on the calc'd value & the only real work around I've found is to manually clean up the view.
-
http://www.infopathdev.com/blogs/hilary/archive/2012/01/19/ipfs-design-checker-errors-amp-print-preview.aspx
This is an error in IPFS - basically, sometimes InfoPath will add binding info to the view for a calculated value that causes an issue when publishing. You can manually remove this info from the view files. Attach your template under the ...