-
Thanks for the reply. I find another way to do this and worked!
In the repeating table added a rule with the condition
If Name from (secondary data) does not contain Name from (txtbox in main data) Hide this control
Now I have another question????
If I want to delete that row record of the Secondary data I ...
-
I am very new to Infopath so please bear with my question. I have designed a field list in Infopath that I am trying to upload in Sharepoint. From Infopath, I uploaded all the field (Column) to Sharepoint, all column works will except for one. This is column basically updates itself if a record on the first column is updated (timestamp). The ...
-
Hello,
In SharePoint On Premises you can use the REST api to do a partial match. I think the filter is StartsWith or Contains. Search for SharePoint list REST Contains and see if you can find some posts.
Good luck!
P
-
Hey, Laurie - so I think you are saying you are getting the same compatibility error as the original poster when you publish to a form library - is that correct? qRules doesn't change the compatibility on your form (it doesn't turn a browser form into a filler form) but it does add code. Forms with code have different requirements ...
-
I'm having the same problem with a SP2013/InfoPath 2013 browser form. I injected it with qRules 7.2, using the site collection admin user account. This is a 2013, browser, sandboxed and I get the exact same issue. the qRules injection process turned the form into a filler form.
I cannot have this ...
-
Thank you Hilary! The postback setting worked!
-
You can promote fields in your form so that data from the form is visible in the library's views - does that do what you need? http://www.bizsupportonline.net/blog/2014/promote-infopath-form-fields-to-sharepoint-library.htm might help.
-
I've built a script to show me all the lists on our SharePoint site that use an InfoPath modified form.
The reason I did this is that we are fairly certain we're going to attach our 2010 db's to a 2013 server.
When we do that, we know we have to alter the way the forms request username due to the claims-based ...
-
I have searched all day for a method to remove the xdado node from the xml and found nothing except doing it manually through notepad. Is it even possible?
removing at form load sounds like the most logical place to remove it, ideally I'd like to stop it from ever being added (I attempted this and got a catastrophic failure - Oops!) ...
-
I've seen this in IPFS before - where conditional formatting doesn't seem to apply correctly and then does as you scroll. I'm not sure of a solution - if you are using buttons for show / hide, maybe try setting postback to always on them?