View Complete Post
I created several forms (Create/Edit/View) for a SharePoint list, using Custom List Forms. I'm using Content Types in the list to ensure that each item only has the necessary fields. When I created the ASPX forms, and inserted the Custom
List Forms, I selected the correct Content Type, and I got the right fields inserted in the form.
Now, for some reason I can't identify, every time I create a new form, and insert a Custom List Form, SPD is bringing ALL fields from the list, instead of just bringing the fields included in the selected Content Type.
I have tried many different things to solve the problem, including creating new lists/content types/forms, etc. but SPD is doing the same thing all the time.
Can somebody tell me what may have gone wrong in SPD or MOSS?
how to deploy a workflow design in SharePoint Designer 2007 in a list from development server to production server.
i create a workflow in a list with SPD 2007 . I want to deploy it to production server who i can do this.
Is there any way to validate those mentioned form at server side? Is it really good way to think that my validation can put inside Event Handler?
We recently upgraded everyone to Office 2010, but we are still using MOSS 2007. Since the Office upgrade, I am getting numerous reports of problems with the 'required fields' of any document be editing (or newly created) when users try to save it back to
These documents are throwing error messages indicating that some required properties 'are missing or invalid'. However all the needed info is indeed there. Even existing documents (that already have the field data in place) are giving the message when a
save (or save as) is attempted. However, if the user saves a copy of the document locally and then manually uploads it via the SharePoint UI, it works fine. It appears to only come up when they use an Office app for editing and try to save it directly back
to the server from the app. This process worked fine with Office 2007.
This only started when the Office 2010 upgrades were rolled out, and (as far as I know) no changes were made to SP at all. I have never seen this phenomenon before, so I would greatly appreciate any advice and/or education on this. :)
What is the best way to update a Sharepoint 2007 custom list schema file (that is deployed using a feature) after the list has been deployed to production.
Scenario: We have custom list based on a custom list definition and template that we have deployed to production. Users have added items to this list and also added their own new columns to this list apart from what we originally included. Now
I want to update this list schema (add another custom column). Whats the best way to achieve that?
Also, a related question is that if a new <field> entry is added to an already deployed schema file, will pushing the new schema file to the right place be enough or will a feature deactivation/activation also be required? I have noticed that some
changes to schema files are picked up without the need to deactivate/activate the feature. But whats the general practice for scenarios like this?
can you please specify where will the sharepoint list data will be saved in sql server?
please throw your thoughts?
Thanks in Advance!
I'm trying to import an excel 2007 sheet into sharepoint 2007 to create a custom list. I get a run time error of 1004. When I click debug I end up in a VBA module BtnPublish at this line : rng.QueryTable.Delete ' delete query table if there is one on the
I have created dummy database, Table in SQL Server 2005 with some values.
Iam able to pull data from the SQL database to sharepoint dataview webpart through data connection using sharepoint desigher.
Now i have to enter new record in to SQL table through sharepoint. i have checked with sharepoint designer but unable get it done.
Can some one have idea on this. Please help me to get it done
Thanks in Advance.