elorg.net

I’ve been working with SharePoint 2010 and Word Automation Services quite a bit these days. I recently ran into an error that I just could not figure out. There’s very little out there on teh interwebs, and the only solution that I found sounded perfect. At first.

When attempting to convert a file from .docx to .pdf via Word Automation Services we were receiving:

Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (D:\Program Files\Microsoft Office Servers\14.0\WebServices\WordServer\Proxy.config line 77)

This was a brand new SharePoint install and everything appeared to be configured correctly. The ONLY solution that I could find was to apply a .NET hotfix (KB976462). It made sense. It sounded perfect! However… the .dlls that the hotfix wanted to apply were at an older version than what was already on the SharePoint server. At this point, we opened a case with Microsoft… (more…)

Strange problems when attempting to add ListViews to the DispForm.aspx (kind of similar to the breakage of attachments of a customized EditForm.aspx).

If you use the trick http://www.sharepointology.com/setup/add-web-parts-to-dispform-editform-or-newformaspx/ to add web parts so that you don’t unghost the page… ListViews added will not display the title, or a border. They’re “stuck” with a default. If you convert it to a DVWP, everything’s snazzy.

If you want to use a query string filter, this also will not work. You will need a DVWP to do this.
TIP!
Add a LVWP to the page using the trick above, then open in SPD and Convert to DVWP. Then setup a query string parameter to filter the DVWP on. As long as you don’t start monkeying with the code, making these changes in SPD doesn’t seem to unghost the page.

Quick tip for you today! I need to do some math on months and don’t want require the users to enter a full date. I created the “Month” column as a number field, no decimals, not required, min value 1, max value 12. Now I’m able to do any calculation that I want on the month value, but my views and DVWPs display the number, and I want to be able to display it as the actual month from time to time.

Attempts:
I created a calculated column that I titled “MonthName”. Here are some quick formulas that you can use in your calculated column that will convert your 1-12 number into a month name.

=TEXT([MonthNumColumn],"mmmm") will give you “December” for a value of “12″
=TEXT([MonthNumColumn],"mmm") will give you “Dec” for a value of “12″
HOWEVER, this seemed to only return values for December and January – and they were not actually accurate.

I thought that perhaps it was because the numbers were not all 2 digit, so I created a second calculated column that I titled “MonthNN” and used this formula (I know, starting to go down the rabbit hole):
=TEXT([Month],"00")
And then adjusted the above calculated MonthName field to refer to this new calculated column. No change.

Then I attempted to use the “CHOOSE” function, but the “Month” field was not required and returned “#VALUE!” for any blank fields.

So I nested the CHOOSE function inside an IF statement, and it’s not the most elegant, but it works:
=IF(Month="","NA",CHOOSE(Month,"Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"))

Enjoy!

I’ve recently been running into problems with search on several WSS 3.0 SharePoint sites. It simply wasn’t returning results. They’re all configured the same way, so it’s no surprise that they’re all experiencing this problem. If it was MOSS, I would’ve had this resolved by now. I’m just not as fluent with WSS and familiar with its limitations. I’ve run out of GoogleFu mojo on this one, and ended up having to go through trial-by-error and spending several days banging my head on my desk before I figured it out. So here it is! (more…)

If there’s one thing that I’ve learned about SharePoint, it’s that there’s about a dozen different approaches that you can take to implement just about anything in it. The “choice” field in SharePoint is no different.

The direct approach is to open the settings of your list or library, and add a new column of type “Choice”. Populate the choice options in the settings, and choose your choice “type” (dropdown, radio, checkbox). The down side to that is in order to edit or add new choices, more than contributor access is required. In many cases, the power users want to be able to add new choices without having to ask for assistance, but we don’t necessarily want to grant additional access in most cases. (more…)