-
Yes, and I know how to do that, but that doesn't mean it can't be undone. I can't imagine why they would disallow the use of a specific SharePoint tool that doesn't require the addition of code to the system but would allow you to insert live, untested code to the production environment. Can you not discuss this with ...
-
That's not enough information. You need to do some troubleshooting and testing first to help yourself or us to figure it out. What does that user's system have? Same level of Office? Same OS? Same screen resolution? Do all other users not see the full text? Do you see it on other computers?
-
Did you mean 4 separate forms or 4 separate views? If it's 4 separate forms, then that's an entirely different beast, but I think you mean 4 views in one form. Hiding sections based off ANY metadata is very simple. Doing it based off a checkbox, whether using Boolean or text, should be a cinch. I don't think ...
-
Just to be clear, you will be allowed to deploy a form with code-behind that must be administratively approved and added via Central Admin, but you can't do non-code modifications with SPD?
-
It will always default to Form1 when using the regular Save/Save As feature. If you want to do something more dynamic and unique, then check out my blog entry: Auto-Generating Filenames for InfoPath Forms.
-
I don't know of any such thing. Can you not speak with the SP administrator to see if you can get a concession for making workflows. At my client, we plan to lock down SPD, too, because it's dangerous in the wrong hands. However, we will have a special server for doing SPD changes limited to certain people, and we will ...
-
Useful Sharepoint Designer Custom Workflow Activities
The activity in question is Send Email Extended, but you may be interested in some of the others, too. These are activities that are not in SPD out of the box but can be added easily.
-
The term "enterprise solution" is too vague? what does that even mean? Just saying it generically, then maybe one would say that IP03 is not generally used for enterprise use, especially with SharePoint. However, IP03 forms can be submitted to SharePoint 2007 for rich client use just like IP07. They can't be ...
-
You can't browser-enable a form created in IP03, but you _can_ create a browser-enabled form in IP07 and make it 2003-compatible. In this case, any user can view it in the browser, but both 2003 and 2007 users can view it in rich client. IP2003 has no option or ability for making its forms browser-enabled.
-
If you use SharePoint Designer to do your workflow and send the emails, then there is a custom action on CodePlex that lets you specify the From address.