SharePoint Blogs

Also tired of running the publish form wizard every time? Especially when you are developing a larger number of forms this can be a frustrating and time consuming task.

This is a description of the post-build steps for automatically building and deploying the forms:

1. Copy the files to a temp dir (Visual Studio creates a lock on the files)
xcopy "$(ProjectDir)Infopath Form Template\*" "c:\temp\$(ProjectName)\"

2. Delete Myschema.xsx - this is not part of the form template
del /Q "c:\temp\$(ProjectName)\*.xsx"

3. Put the folder in a cab file (download the CAB tool here)
cabtool c:\temp\$(ProjectName)

4. Rename the CAB to XSN
ren "c:\temp\$(ProjectName).cab" "$(ProjectName).xsn"

5. Deactivate the previous edition of the form
stsadm -o deactivateformtemplate -url http://yoursite -filename "c:\temp\$(ProjectName).xsn"

6. Remove the previous version of the form
stsadm -o removeformtemplate -filename "c:\temp\$(ProjectName).xsn"

7. Kick the job service (saves you the wait)
stsadm -o execadmsvcjobs

8. Upload the new template
stsadm -o uploadformtemplate -filename "c:\temp\$(ProjectName).xsn"

9. Kick the job service (again)
stsadm -o execadmsvcjobs

10. Activate the new form template
stsadm -o activateformtemplate -url http://yoursite -filename "c:\temp\$(ProjectName).xsn"

11. Clean up the mesh 
del /Q "c:\temp\$(ProjectName)"
del /Q "c:\temp\$(ProjectName).xsn"

This will result in:
xcopy "$(ProjectDir)Infopath Form Template\*" "c:\temp\$(ProjectName)\"
del /Q "c:\temp\$(ProjectName)\*.xsx"
cabtool c:\temp\$(ProjectName)
ren "c:\temp\$(ProjectName).cab" "$(ProjectName).xsn"
stsadm -o deactivateformtemplate -url http://yoursite -filename "c:\temp\$(ProjectName).xsn"
stsadm -o deactivateformtemplate -url http://theirsite -filename "c:\temp\$(ProjectName).xsn"
stsadm -o removeformtemplate -filename "c:\temp\$(ProjectName).xsn"
stsadm -o execadmsvcjobs
stsadm -o uploadformtemplate -filename "c:\temp\$(ProjectName).xsn"
stsadm -o execadmsvcjobs
stsadm -o activateformtemplate -url http://yoursite -filename "c:\temp\$(ProjectName).xsn"
stsadm -o activateformtemplate -url http://theirsite -filename "c:\temp\$(ProjectName).xsn"
del /Q "c:\temp\$(ProjectName)"
del /Q "c:\temp\$(ProjectName).xsn"

Additional tip:
Once you switch from a Debug build to the Release build you should:
- manually remove the pdb files from your manifest file
- remove the pdb files from your project directory

---

Posted on SharePoint Blogs

Body: I was recently contacting by someone putting together a book on Office Communications Server 2007. They're looking for someone to write an appendix regarding OCS and MOSS (mostly regarding Presence), along with Project Server. I haven't Read More......(read more)

In sharepoint you can either create a personal or a public view on a document libraries, lists etc. You may come across situations where you need only a few individuals to see a particular view.

Lets take an example

 Your have a custom list containing software contract information like customer, license type, product, contract date,contract currency, contract amount etc. You are required to allow everyone in the sales department to see this list however the contract amount should be visible only to few management executives. You may create 2 public views, one that has the contract amount and the other that does not. The next step would be to provide read-access to the list to all the people in the sales department.

In sharepoint, if you give read access to a list or library, the person will also have read access to all public views. which means, by default everyone is able to see both the views, one with the contract amount and the one without. Not being able to control access on views seems to be a design flaw/gap in sharepoint. I hope Microsoft will address this in the next release or a service pack. Until that time, here is a workaround that may work in some of the cases

On the list where you want to restrict access to views to a few individual:

• Create a column called "Restricted users".
• Column Type = Person or Group
• Allow Multiple Selections =Yes
• Allow Selection of = People Only
• Choose From = All Users (This is the list of Users from your Active Directory(
• Show Field= Name ( Choose this from the drop down)

Lets say John Smith and Jane Smith are 2 executives who need to see the list views with the contract amount

Open up the list in data sheet view.  [List Name]>>Actions>> Edit In Datasheet

Scroll to the column called "Restricted Users"

Under the column, in the first cell type John Smith;Jane Smith  ( These 2 names should be in AD exactly as spelled, if not find the correct spelling)

Copy this cell to the rest of the cells under the "restricted users" column and save.

Create a view for this contract list, call it "Contract-Restricted"  or an appropriate name. This view should be created as a public view.

In the filter section where it says "show the items when"

• Choose "Restricted Users" from the dropdown list
• Condition =Is equal to
• In the text box type [Me]

When sales people login to the site and selects the list, they will see both the views but when they choose the "Contract-Restricted" view, they will not see any results because of the filter.

The filter essentially looks at the current user logged in sharepoint, if it is John Smith or Jane Smith, the filter condition is met and it returns the result in the "contract-restricted" view otherwise the view will not return any result.

 

 

---

Posted on SharePoint Blogs

Looking for some free SharePoint training ? Tomorrow is your day! The SharePoint Pro Online virtual conference is tomorrow from 11 AM - 4:45 PM EDT (GMT -0500) . I'll be presenting with a handful of other SharePoint professionals on various topics Read More......(read more)

Have you seen this error before? Did you find a solution? I was getting this javascript error on the click of a button that had a simple rule attached to it. Everytime I clicked the button, it produced this javascript error: Null is null or not an object. After some debugging, I noticed that the error was occuring in the "owsbrows.js". This file contained a line that was trying to load a value from the control that was clicked in the form. The control returned "null" and hence...(read more)

I had a button in my form and there was a simple rule attached to this button. Rule was that If someone clicked the button, a (hidden) textbox would appear in the form, a very simple rule! Problem?? The button was not working. Somehow the event was not firing. I had this problem even before but simply changing the ID of the button resolved my problem but this time, changing the ID didn't work. I spent a couple of hours trying to find the cause but in the end, I needed a quick solution as I was...(read more)

I watched a video with Andrew Connell, and it was brought to my attention that Custom Field Controls may be more appropriate than custom web parts in certain situations...  One question that I have is if the tool pane is accessible for the end user when dealing with a field control...  Can the design set configuration data from sharepoint designer?  Please post any thoughts you may have.

---

Posted on SharePoint Blogs

When working on large applications, we usually make mistakes and then spend time debugging the errors that occur because of the mistakes that we make during programming but there are some errors that occur even if you don't make any mistake. Have a look at the following code: SPWeb web = Site.OpenWeb(SPContext.Current.Web.ID); string strList = SPContext.Current.Web.Url.Substring( .... substring processing ....); SPList list = web.Lists[strList]; //This line gives error! Do you see any problem...(read more)

Body: I was listening on my new Zune to a podcast at Michael Gannotti's blog which was entitled WSS vs MOSS for Internet ( MP3 link ). In this podcast, Michael shares some of his thoughts on what appears to him to be shortcomings of Windows SharePoint Read More......(read more)

I have a long way to go and I am thankful to the 800+ RSS Feed subscribers for joining me in this journey. Over the past few months, I have had some tough trials and tribulations. From switching to a full time consulting gig to reorganizing my efforts Read More......(read more)