Tips & Tricks from Linda

Nowadays, more and more people work in IT industry as a software developer. Have you think about that to be a 'successful' developer? How do I find a dream job, grow my career and even start my business? How to survive? Then you need to develop Soft skills which the book  Soft Skills: The Software Developer's Life Manual  helps you to achieve your goals and enjoy your life in following areas: managing your career, dealing with clients, peers, and managers, staying productive, achieving financial security, and keeping yourself in shape, etc.  Although the book title says"software developer's life manual", it's not a technical book and is helpful for other professional. The book is comprised of 7 sections: Career, Marketing, Learning, Productivity, Financial, Fitness and Spirit. Just list some existing sentences here: "Creating your first product - As a software developer, you’re in a unique position to be able to be an entrepreneur who no

If you want to replace the Out of Box SharePoint Help with your custom help page when people click on "?" icon on the top right corner on the SharePoint Portal 2013, then you can use below jQuery in HTML master page. The sample screenshot is as following. You need to reference to the "jquery.SPServices-2014.02.js" file firstly.     var currentSite=$().SPServices.SPGetCurrentSite();   /*Replace ms-help element onclick event*/   $("#ms-help>a").attr("onclick","abc");   /*Replace below "Pages/PortalHelp.aspx" with your actual custom Help page location*/   $("#ms-help>a").attr("href",currentSite+"/Pages/PortalHelp.aspx");     $('#ms-help>a').click(function(){               window.location.href=currentSite+"/Pages/PortalHelp.aspx";     }); This post is part of my BI Portal project . If you are interested to know more how I customized a Out Of Box Bu

Most of the BI consultant don't know how to customize a out of box BI SharePoint portal, and I had been worked on the project to develop and implement a on premises Business Intelligence SharePoint 2013 Portal for Reserve Bank Of Australia. I would like to share my experience on the customization process in here. I created the site branding including HTML master page, custom jQuery and CSS.  The style references to an existing SharePoint 2010 site. The site uses the kerobers authentication for user logon and integrated with Reporting service, Power BI and Quick View application. I tested the site with Google WAG tool and fixed related WAG issues ( see my post ). I also fixed those security issues from the bank security testing result conducted by the bank.   Below are the screenshots of the portal. Portal home page Power BI Library See my posts related to this project:  Specific configuration to enable search Power BI files in SharePoint Replace th

The DEECD (Department of Education & Earlier Childhood VIC) needs to upgrade the branding of several Public facing Sites from SP2010 to SP2013 platform.  I upgraded the existing look & feel in SP2010 to SP2013 and also made their mobile site using SP2013 new branding functionalities. I developed the customed HTML master page, CSS and jQuery file for below web sites. I also troubleshooting a "The Design Branding Package creation failure issue" which related to a SharePoint 2013 bug confirmed by Microsoft (see my post here ). Below are screenshots of some Web sites in desktop & its mobile site. The above content in mobile view won't be seen in the desktop view of the Website. It only shows when in the page editor mode. The Web site for Deaf user.

If you want to restrict to only upload Powe BI file (.pbix file) to “Power BI Library” as below screenshot, you can use following JQuery code in HTML masterpage. //Check upload file extension is PowerBI files - only for Power BI Library CheckAssetLibMediaExtension = function(){ if (window.parent.location.pathname.toLowerCase().indexOf('powerbifiles')>0) {       var allowedExtensions = /pbix/;       var inputFile = $("input[name$='InputFile']").val();       var ext = inputFile.substr(inputFile.lastIndexOf('.') + 1);      console.log(ext);       //var      $currentIFrame = $('.ms-dlgFrame');     if (!allowedExtensions.test(ext)) {           $("input[name$='btnOK']").attr('disabled','disabled');            alert('Only Power BI file with file extension name is .pbix can be uploaded                  to this library.');  $currentIFrame.contents().find("body .ms-error")

By default, the Microsoft Power BI report file (.pbix) is not in the list of file type in SharePoint 2013 search configuration in Central Admin, and so you wouldn't open the Power BI file directly by clicking the link from the search result page. However, it's easy to add this file type by following configuration. Open “Central Admin” site, and then go to "Manage service applications”->”Search Service Application XX” (use the actual name of the “Search Service Application” in your site). Click on the “File Type” in left side navigation. Click the New File Type button and type PBIX (no period needed) in the File extension box and click OK. Restart the Search Service: Go to local “services”, stop the SharePoint Server Search service and start it again. Reset Your Index: Back on the Search Administration page within Central Administration you will want to click on the Index Reset link under Crawling on the left side menu. Press the Reset Now button. Rem

I had been worked on a SharePoint 2010 Internet sites upgraded to SharePoint 2013 project in 2014. The SharePoint 2010 site was customized with some farm solutions.  I experienced the Design Manager Design Package creation failure issue in SharePoint 2013 which upgraded from SharePoint 2010. The Design Package was used for the site branding deployment. I added the branding sources files including JavaScript, HTML master page, CSS and images to another clean out of box site collection and then the design package can be created successfully on there. But after deployed those custom farm solutions to this site collection, and package creation was failure again.    So I started to look at this issue around those custom solution. I found out the root cause of the design package creation failure was the special character (ASCII) ▲ added to the custom property bag value. I went to SharePoint designer and then clicked on “Site Options”, and then removed above character from