-
There are 2 ways to get promoted fields when publishing to SharePoint. One is to set up the promoted fields during the publishing wizard. This is a one-time deal and needs to be done every time you publish. The other is to go to Tools | Options and permanently set up your promoted properties.
-
Your problem most likely stems from different namespace definitions between the two XML documents.
For example, you might have <my:Root><my:Field/></my:Root> in two different documents, but the my: namespace might have a different definition in each
Doc1: xmlns:my="definition1"
Doc2: ...
-
Strange... sounds like some issue more with the backend, but it could be InfoPath (just doesn't seem like it).
Maybe try setting up a SPROC and calling that instead of directly running a SQL command. Maybe that will solve the prolem.
Outside that, I don't know.
-
Contrary to how it sounds... conditional formatting on a repeating table only hides rows, not the whole table. If you want to hide the entire table, you need to place the table into a section and add conditional formatting on that section.
-
Look into using conditional formatting on your table. Hide the row if the user should not see it.
Filters are more preferable, but unfortunately do not work on secondary data source tables... so you'll need to use conditional formatting.
-
Have you used the debugger on this to verify that the Command property contains what you expect it to before running the Query()? You'll want to verify that strNewStatus and intHolydayNr are valid values and that the command string is being created properly.
Also use a try/catch to see if there's something else going on.
-
My guess of what's going on is that you already have a value in: my:field4. So before you do anything else (before you get all the nodes), you need to clear the value of this field...
thisXDocument.DOM.selectSingleNode("/my:myFields/my:field4").text = "";
-
Glad to hear you got it working. Thanks for sharing your solution with us.
-
Your close --
The line you've highlighted is in the <xsl:otherwise/> -- which means that this option gets displayed function-available('xdXDocument:GetDOM') fails (a rare thing).
Leave that modification that you made, but where you really need to make the change is ...
-
Great! Glad that worked for you. Not sure why your event handler was broken, but glad its fixed now!