15 Ways to Become a Better Leader in 2015 | Switch & Shift.
First rule: Don’t take Company Culture for Granted…Noted
I went to the January SharePoint Users Group today. The speakers where the incomparable Laura Rodgers and Lori Gowin. They were practicing their talk on User Adoption Issues that they will be giving at SPTechCon in just under a month.
As always these two are packed with knowledge and they are happy to share it.
yea, so I have this crazy requirement…
I have like 30 fields that are required on a form. We have created a ‘warning section’ that must show a warning to the user stating which required fields are not yet filled in. On the surface not really that big of a deal, only we cannot add ‘code behind’ on this form. What to do? Tap into some mad Rulez Skillz and consult the Interwebs for a crazy @$$ expression…
so I built an awesome expression, tested it and bam, not the result I wanted…I tried grouping expressions and no go…back to the drawing board…
well, I have built this expression seems like a shame to let it sit there and waste away…now what? During troubleshooting I used the expression to populate a field, so I could see that it was setting true or false…then light bulb!!! I can set a rule on the section to wait for that field to become true, then hide the section…
That is what my friend Keyur calls ‘Bam!’ So finally, I have a warning section that hides or shows properly based ont eh required fields being filled in…nice…
I forgot to add a the expression, it looks a little bit like this
boolean(../my:field1 != “” and ../my:field2 != “” and ../my:field3 != “” and ../my:field4 != “” and ../my:field5 != “” and ../my:field6 != “” and ../my:field7 != “” and ../my:field8 != “” and ../my:field9 != “” and ../my:field10 != “” and ../my:field11 != “” and ../my:field12 != “” and ../my:field13 != “” and ../my:field14 != “” and ../my:field15 != “” and ../my:field16 != “” and ../my:field17 != “” and ../my:field18 != “” and ../my:field19 != “” and ../my:field20 != “” and ../my:field21 != “” and ../my:field22 != “” and ../my:field23 != “” and ../my:field24 != “” and ../my:field25 != “” and ../my:field26 != “” and ../my:field27 != “” and ../my:field28 != “” and ../my:field29 != “” and ../my:field30 != “” and ../my:field32 != “”)
Some projects are better than others, or are they? Or are they better in some ways and worse in others.
We have a project that started out as A and is turning out to be not B, not C, more like L3.0…as a developer it has been a lesson in patience, as a professional it has been full lessons that build skills and techniques. We have had to build a completely custom UI atop InfoPath forms. Forms that have bloated rules for just about every control. In retrospect we would have built this in .net atop SharePoint. There’s way more, but I am out of time for this. Later!
Alright, so we were recently faced with a challenge. Client has a bunch of templates they use locally on desktops that they want to be more efficient with as part of a conceived application and workflow process in SharePoint. Simple enough, right, create content types, add columns, insert Document Properties into the Document Content Types and Bob’s your Uncle. Well, not quite. This client gave us their ‘Templates’ and this included 13 Word Documents and 1 Excel Document.
They had presented this to another consultant as well as their in house IT team. All had come up with relatively the same set of ‘solutions’ to the problem. What’s the problem? you ask…The problem is that you cannot add document properties, natively to Excel Documents in the quick and easy manner that you can, say a Word Document. We discussed the problem, and like so many before came up with the same possible solutions:
1. Create an InfoPath form to collect data and present it to users via PDF Output (ultimately that is where it needs to go)
2. Create a Word Document version of the Excel Workbook and let users interact with that.
3. A Variety of equally non-workable solutions for the client.
You see, they like the functionality of Excel. There are cells that have formulas and they want to be able to be flexible with those formulas, dynamic even. Which is to say some of the content in the excel workbook comes from the list item in sharepoint, but some of it is manipulated on demand by the user…Word, might could do that. Word with an embedded excel workbook object might could do that, but none of them were quite right.
Which is what leads me to the VERY helpful link above. ‘But, Bill, that is for BuiltinDocumentProperties, and SharePoint Server Document Properties are not in that collection.’ That is correct, however ActiveWorkbook also allows for ContentTypeProperties which exposes the full gambit of Server Document Properties. Note in order to use this, however, you must have the document in a Document Library with properties attached.
Now that I have my modified User Function (based on the link, thank you Gord Dibben), I can now place the formula =DocProps(“xxxxxxx”) and reveal the Metadata in the Excel Document correctly.
So now, user fills out InfoPath Form on list item, on submit, workflow creates several Word Documents and 1 Excel Workbook from Content Types, saves them in a Document Library, and populates Metadata on each newly created document and workbook.
This is an issue we have faced before, and like so many others created work arounds for clients, this time, that was not an option, and so we found a solution.
While looking for a resolution to an issue with filtering a SharePoint 2010 List View, I came across this. We have a column that is a multi-line text column that is populated via workflow with the userids of members of a group.
After some consternation trying to resolve using the [Me] or the [Current User] option with a contains, I had just about given up.
resolution though in the form of…open the page in SharePoint Designer and locate the webpart hosting the list. It is a Data View Web Part, go to the Filters section and create a new filter: choose your column, choose contains, choose new parameter. create this new parameter based on Server Variable Logon User.
Bam! mission accomplished…or at least this battle won. I live to fight the next battle