.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Promote new field to existing forms

Posted By:      Posted Date: October 01, 2010    Points: 0   Category :SharePoint

Using MOSS 2007 with InfoPath browser enabled forms.  Have about 600 existing forms.  I added a new field to the template and successfully promoted the field to the content type.   However, the field will not be added to the xml for existing forms until each form is opened and submitted.  But we have a workflow that will need to update this new field with a value once a certain date is reached.  The workflow will be unable to set the field on existing forms that have not yet been opened/submitted.  We want to avoid having to open/submit all forms each time we promote a new field.  Is there a programmatic way to handle this (injection of the field into the xml perhaps)?  Or is there a task in SharePoint that can be executed to do it? 

 Please help!!  Thank you!!

View Complete Post

More Related Resource Links

Overwriting Existing InfoPath 2003 Forms



I'm having a big problem in my Sharepoint Environment.

So far I've created a form in InfoPath 2003 and successfully published it to a Form Library. It's also submitting correctly (at least at first).

Now after I added a couple forms, let's say three forms with unique file names, and then I open the second one, make a change and submit it again, it disappears from the "All Items" list. I can still see it sitting in the "Explorer View", but it's missing in the other. Now when I try to "Fill out a new Form", it either won't show up in the list or it will show up but with the column fields that have been populated previously.

We're using WSS 2.0 and InfoPath 2003.

I used this guide to create the unique filenames: http://www.codeproject.com/KB/sharepoint/SharePointSubmitInfoPath.aspx

In my view, the issue lies in trying to overwrite existing files and not appearing in the list.

Any help is much appreciated !!!


Thanks in advance.

Marvin Sugirin

Issue Adding a new Lookup Field to an existing List Instance

I have a code base that houses all of the column, content types, template, and list instance definitions. Am using the Update functionlaity a lot from version to version. Has been working well to this point. I just added two new columns (fields), one a Lookup and the other a Multi-Lookup. The fields are added fine on the update, columns look correct and the content type to which these were added also look fine. I can create a new List instance from the content type, and the new lookup columns are fine. The problem is this. Any existing list instances that were created from this same content type, now blow up when I try and access list items via the SP GUI. Something about a valid GUID, I dont't have the exect error anymore, but will repost it when I recreate the issue for the tenth time. I tried deleting the new lookup fields from this new list instance, thinking that I might be able to re-add them to fix the problem, but I get a new stack trace when I try and re-add them. Any hints on where I can start digging would be appreciated. I think I'll start with comparing the list instance schemas between an existing list and a newly created one.  

sp v2 - possible to add a field to existing Lists by script?

thousands of meeting workspaces in V2.0 only one doc lib in each, docs to be migrated to moss, without folders, so need to identify where it came from, am thinking add a column prior to migration, but don't know if possible. Alternately I could first migrate into moss, then add column, then migrate again, but very time consuming for that first step, even if it runs by itself. i am not a programmer, my appologies if this belongs elsewhere, but i'm hoping a developer may have some idea. Thank you, ps: migration to be done with DocAve or Metalogix, because cross-domain, and V2.0 had custom defs, so database upgrade not possible.

Update Existing Sharepoint List's field Problem



This is about sharepoint sequential workflow using visual studio.

I ve a prob to updating existing sharepoint list's field on the basis of other field(id or somthing else), using visual studio.

I m updating sharepoint list but its adding a new row below at last in the sharepoint list.

i m having a UserID(lots of user's ID) field in the sharepoint list, on the basis of this userID i ve to update a perticular field corresponding to UserID.

Please tel me wat type of code i ve to mension.


Thanks in advance !

Regards- Sharad

Create a task list from existing task lists based on field values


Hi!  I have a bunch (~10) of different task lists corresponding to different projects; each list has a mixture of Statuses, i.e., some completed, some In Progress, some Not Started.  I'd like to create a (preferably dynamically updated) single task list consisting of all the incomplete tasks from each of the project lists.  After much trial and error (I'm still a relative newbie with DB stuff; even more so w/ Sharepoint stuff) I figured out how to do this by viewing the lists in Access and creating a query which resulted in the compiled list I describe above; however, when I clicked on the "Publish" to Sharepoint button and returned to Sharepoint default view, I couldn't find this new list anywhere (e.g., the new, empty list I had created and changed to Access view, and from which I imported the other lists and created my query, was empty, and my list of task lists in the left side-bar didn't have my query-result-list).

How do I do what I want, w/ or w/out Access?  Thanks!


Routing for Web Forms in ASP.NET 4.0

posted a prototype demonstrating how one could use Routing within Web Forms. This is something you can do today with ASP.NET 3.5 SP1, because of the work we did to separate Routing from ASP.NET MVC. I would have liked to include Web Form Routing as part of the Routing feature when we were working on SP1, but we didn't have the time to do so in a robust manner before SP1 was locked down.

Application Architecture in Windows Forms 2.0

Applications have special support in Windows Forms. For starters, you can manage and tailor your application's lifetime, and, when the work flow is disrupted by an unhandled exception, you can choose from several methods of response. Then, there are several application models that you can employ, including Single Document Interface (SDI) and Multiple Document Interface (MDI) applications, each of which can support either multiple-instance or single-instance mode, the former the VS05 default and the latter requiring special consideration. All applications, however, can discover and use a wide variety of information about the system and environment they execute in.

Application Architecture in Windows Forms 2.0-Single-MDI Applications

Consider an MDI application like Microsoft Excel; files opened from the file system (by double-clicking) are all opened as separate child windows within the parent Excel window.7 For the first instance of an MDI application to open a new child window to display the file that was passed to the second instance of the application, the second instance must be able to communicate with the initial instance.

Explained: Forms Authentication in ASP.NET

This module explains how forms authentication works in ASP.NET version 2.0. It explains how IIS and ASP.NET authentication work together, and it explains the role and operation of the FormsAuthenticationModule class.

Using Forms Authentication in ASP.NET - Part 1

Classic ASP developers often had to "roll their own" authentication scheme, however, in ASP.NET much of the grunt work has been taken out. This article outlines how things have changed and how FormsAuthentication can be used to secure a Web site with a minimal amount of code.

ASP.NET Forms Authentication - Part 1

Often, in legacy Web applications, users authenticate themselves via a Web form. This Web form submits the user's credentials to business logic that determines their authorization level. Upon successful authentication, the application then submits a ticket in the form of a cookie, albeit a hard cookie or session variable. This ticket contains anything from just a valid session identification access token to customized personalization values.

ASP.NET forms authentication with roles

.A timeout is specified in minutes. This is "time since last request" not the "time since login". If a login is indicated to be persistent (described later) this is ignored.
.A protection method is specified for the cookie.
Next I wanted to specify a folder to which access is restricted to people who have logged in. To do this I entered the following code in the web.config file (beneath

Forms Authentication in ASP.NET

In this tutorial you will learn about Forms Authentication in ASP.NET 2.0 - Forms Authentication class, Cookie Domain, Forms Cookies, The Login Control, Signin, Signout, Authenticate, Redirect, Login Status, Login Name and Login View Controls.

Determine whether Forms Server is installed on a server

Check whether the Microsoft.Office.InfoPath.Server.dll and FormServer.aspx files are installed on the server.

How to programmatically add controls to Windows forms at run time by using Visual C#

Create a Windows Forms Application
Start Visual Studio .NET or Visual Studio 2005 or a later version, and create a new Visual C# Windows Application project named WinControls. Form1 is added to the project by default.
Double-click Form1 to create and view the Form1_Load event procedure.
Add private instance variables to the Form1 class to work with common Windows controls. The Form1 class starts as follows:

How to Localize Windows Forms and Change the Language at Runtime

Localization is the process of customizing your application to a particular language, culture or locale. Visual Studio provides support for localizing Windows Forms with much ease. In this article, we will see how to localize windows forms and give the user the ability to change to his preferred language at runtime.
When you run a localized application, the appearance is determined by two culture values. The UICulture property is used to specify which resource files will be loaded for the form. The Culture property, on the other hand, determines how strings such as dates, numerals, and currency amounts are formatted.
Let us see the steps required to create a localized form. You can then expand this example and adopt the same approach for the rest of the forms in your project

Localizing Windows Forms

The Visual Studio project system provides considerable support for localizing Windows Forms applications. There are two ways to generate resource files using the Visual Studio development environment: one is to have the project system generate the resource files for localizable UI elements such as text and images on the form. The resource files are then built into satellite assemblies. The second way is to add a resource file template and then edit the template with the XML Designer. A reason for doing the latter is to make localizable strings that appear in dialog boxes and error messages. You must then write code to access these resources.

This walkthrough topic demonstrates both processes in a single Windows Application project.

You can also convert a text file to a resource file; for more information, see Resources in Text File Format and Resource File Generator (Resgen.exe).

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend