You searched for the word(s): 12
-
Does the command fail with the same error as your initial post? If you change the lookup column to text (temporarily) does a value get submitted there?
The only thing that looks off to me is the mapping for your referral field:
/my:myFields/my:General/my:referral
I would use XPath relative to the repeating group:
../../my:referral
Your rules ...
-
Hilary,
I got a chance to try this out and followed your steps but I'm still not able to set the value in the lookup column in the Keywords List.
Can you have a look at the rules on the Submit button in the attached form to determine if I am doing this correctly?
Many thanks,
Padraic
-
That's great. I'm using C# in my InfoPath and what I really need is sample code that would show me how to code mine. I need to be able to take my purchase request form with several line items and produce a purchase order in GP.
Joel
-
Clay easily created one. I was going to pursue some development work with him, but our business slowed due to the recession so dollars for such development projects have not been available. I still am intersted in it. For sales orders and RMAs as well. I have parts of it down pat but not 100%.
-
Hi
Just wondered if you managed to resolve this issue.
I have the same issue on a user's PC running Windows 7 64-bit
I managed to workaround the issue by closing Internet Explorer while using Infopath 2007 ,which allowed the Cut / paste functionality to work again.
Thanks
Ian
-
Has anyone used InfoPath to create a PO in Microsoft Dynamics since your post? If so I could really use some help. Thanks, Joel
-
What process are you using to publish the form to SharePoint?
-
New error: Action: SaveToSharePoint. Arguments: url: https://intranet.viauc.dk/it_gammel/intern/udvikling/projekter/print/Attachments xpath: /my:mineFelter/my:File . Details: Security Exception - please check security requirements for this command.
I do get a lot of warnings when I upload the form and in Design Control I get an error ...
-
Thanks Michael.
The node names are case sensitive, so I think it's just a matter of renaming your nodes so that they match the same case as shown in the error message.
Can you try that? Thanks!
-
Hi
Screenshot attached.
/Michael