We have to be deliberate in how we do this with SharePoint because the Title column is required by default.
Posted by Jim Bob Howard on Tuesday, July 13, 2010 at 10:00 am
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, Javascript, jquery, MOSS, sharepoint, Sharepoint Designer, solutions, wss
SharePoint: Extending the DVWP – Part 17: User-Managed Dropdowns – Creating a Relationship list
Posted by Jim Bob Howard on Thursday, July 8, 2010 at 10:00 am
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, Javascript, jquery, MOSS, sharepoint, Sharepoint Designer, solutions, wss
SharePoint: Extending the DVWP – Part 16: User-Managed Dropdowns – Loading Data
Posted by Jim Bob Howard on Tuesday, July 6, 2010 at 10:00 am
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, Javascript, jquery, MOSS, sharepoint, Sharepoint Designer, solutions, wss
SharePoint: Extending the DVWP – Part 15: User-Managed Dropdowns with Site Columns
Posted by Jim Bob Howard on Thursday, July 1, 2010 at 10:00 am
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, Javascript, jquery, MOSS, sharepoint, Sharepoint Designer, solutions, wss
Four articles from now, you’ll have cascading dropdowns on your DVWP. And you’re list owner will manage the content and the relationships from SharePoint lists.
Posted by Jim Bob Howard on Tuesday, June 29, 2010 at 12:00 pm
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, Javascript, jquery, MOSS, sharepoint, Sharepoint Designer, solutions, wss
You could add the PreSaveAction() JavaScript section directly to the page in SharePoint Designer (SPD). You could even add it to the master page, if that made sense for your project. But, I usually add it to a Content Editor Web Part (CEWP).
Posted by Jim Bob Howard on Thursday, June 24, 2010 at 10:00 am
Filed under jquery · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, MOSS, sharepoint, Sharepoint Designer, solutions, wss
As part of the series, Extending the DVWP, we’ve been talking about creating a workflow that fires from a form action.
Posted by Jim Bob Howard on Tuesday, June 22, 2010 at 10:00 am
Filed under Workflow · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, MOSS, sharepoint, Sharepoint Designer, solutions, wss
As part of the series, Extending the DVWP, we’ve been talking about creating a workflow that fires from a form action.
Posted by Jim Bob Howard on Thursday, June 17, 2010 at 10:00 am
Filed under Workflow · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, MOSS, sharepoint, Sharepoint Designer, solutions, wss
In the last four articles, we’ve talked about creating a workflow from Dataview Web Part (DVWP) form action links. In the process, we’ve learned that you can pass Form Fields to the workflow, which is pretty powerful in itself.
Posted by Jim Bob Howard on Tuesday, June 15, 2010 at 12:00 pm
Filed under Workflow · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, MOSS, sharepoint, Sharepoint Designer, solutions, wss
You can now call a workflow from your DVWP and access the content the user just entered or edited.
Posted by Jim Bob Howard on Thursday, June 10, 2010 at 12:00 pm
Filed under Solutions with Tools · Tagged 2007, 2010, Content Editor Web Part, Data View Web Part, MOSS, sharepoint, Sharepoint Designer, solutions, wss