SOFTware is HARD

Objective I needed to prepare an Excel file for importing into SharePoint. Excel First, I need an Excel formula to populate a short name (255 characters) from a much longer name ( found in "col"). The length of the short name is constrained by SharePoint's "single line of text" field. The challenge is to find acronyms within col or if am acronym can't be found, to truncate col to 255 characters. Example:  GNU is Not Unix (GNU) => GNU This is another name => This is another name This is the formula to use.  = IF(ISNUMBER(FIND("(";[col]));MID([col];FIND("(";[col]) + 1; FIND(")";[col]) - FIND("(";[col])-1);LEFT(CLEAN(TRIM([col]));255)) Importing into SharePoint The only error free way to do this is to use Excel to export into SharePoint. Create an Excel table and select it Go to "table tools" tab and choose the "export table to SharePoint list" option within "export...

The logical model metadata The physical model metadata Note that Blue denotes the RDBMS metadata while Green denotes the NoSQL metadata.

Although I'm aware of the downside of using folders in Document Libraries, I still think it's one of the best ways to categorise files. This is especially true when migrating from file-shares to SharePoint. Furthermore, it's a great hassle to individually tag metadata or column information for each file that I wish to dump into SharePoint. To workaround this issue, the solution is to use automatic tagging in conjunction with the use of folders. See here However, if you structure your Document Libraries with many folders and different levels, you will quickly end up with a different problem: Having to set-up the rules (mapping) for each folder using SharePoint. The easiest way to get around this is to edit the rules directly. This file can be found in the hidden Forms folder as client_LocationBasedDefaults.html. By opening the Document Library using Windows Explorer, you will be able to edit the file. Do so with great care!

UML appears to be dying in the light of the Agile development movement. working software over comprehensive documentation Many have wrongly interpreted this to mean no documentation. I recently read up C4 model for software architecture that describes the software architecture of a system from different depth & perspectives and for a different audience. The author promotes the use of a common vocabulary to describe software architecture using simple-to-understand diagrams. I attempt to do similar in this post using the same case study as that of the C4 article. The differences are: I do not wish to go into  Class (the 4th C) as that requires too much implementation details I replace the 4th C with Concept as I personally find the Conceptual model more relevant and important in appreciating the business domain.   Using Astah , I figured out how I can model the 4C software architecture efficiently using UML. Mind-Mapping I started with a Mind...

I had the requirement to map the default column values of documents to the nested folder structure it is created/ uploaded into. As an example, a document uploaded into \Document Library\2018\Jan\DeptABC would have default column values accordingly: Year: 2018 Month: Jan Dept: DeptABC The column values (metadata) make searches effective and rather than to have users provide the metadata as a distinct step, we determine the metadata based on the logical (directory) location of the document. To manually configure this, go to [Library Settings] -> [Column default value settings] See here . However, if there are too many columns to configure, a quicker way to do so is to edit the mapping file directly. This file is found in the root of the library: " Forms\client_LocationBasedDefaults.html ". It is an XHTML file that isn't too difficult to comprehend. Do be careful and backup the file before editing.