Technology Tips -

Monday, March 7, 2016

We have written a lot about share point designer before but this time we thought there should be more information for share point designer written as this is becoming very import for all designers who are working with share point technology.
Microsoft initially introduced FrontPage for editing webpages earlier then discarded that product and people might have worked with expression web for creating web pages and then Microsoft introduced SharePoint designer which was corresponding tool for SharePoint for designing SharePoint sites.
And probably Microsoft has changed direction when people have seen Microsoft is launching Microsoft edge with windows 10 would be used for designing and enhancing SharePoint sites.
Microsoft is coming up with new ideas of browsing and enhancing it with Microsoft edge with windows 10 browser – you can change and enhance your web experience through thin client which
is Microsoft edge browser where you read content and write as well.
So again web designer still thinking to work with the right tool, when it’s coming to enhance and customize existing SharePoint site so everyone ending up with ms SharePoint designer 2013 because people are working with sharepoint 2013 but how they can customize site easily.
Ultimately people are using SharePoint designer 2013 but it does not have WYSIWYG editor so web designer still finding some other ways to design sites.

MS SharePoint designer 2013 with Dreamweaver:


You can use sharepoint designer and dreamweaver  for designing master pages  or if you wanted to design a header in any html editor and take them into SharePoint designer and other component and publish them in your SharePoint site.
You have choice to design your header or social bar with any html editor, it could be Dreamweaver
Ideally you can find some slider on net and download it and open it in Dreamweaver
One of the major components of sharepoint designer 2013 is design manager with the help of design manager in SharePoint 2013 you can channelize your master page specific to mobile or desktop or ipad so once configured different master pages will be used for different channel.
Ideally you can use Dreamweaver for designing header as master page and import it using design manager so the entire header layout will be converted with design manager. These headers will be treated as master page and will be converted automatically from design manager.

This means you add social bar in Dreamweaver and update it by time to time in dreamweaver and change will be reflected in SharePoint once you have uploaded all design file into associated libraries in sharepoint then this bar up and running.
If you have multilingual site so you must be having 2 default.html 1 for English and 1 for Arabic and 2 more files associated with them as .master file each and if you have header navigation so must be having header.html and header.master. But you have to edit your html in dreamweaver for any header you have designed there and changes will be synced automatically because you have uploaded all html files from design manager and SharePoint just created .master file for all those header pages.
You can design any social bar or navigation in that header and convert them into master using design manager.
So as of now you can understand how to design navigation and where to design it obviously in dreamweaver or you can design consistent look for all pages as master page that will be used as master page later. One more thing which is very important to explain you can also design navigation in SharePoint 213 for that you don’t need SharePoint designer or Dreamweaver.
But still there is a need of slider in SharePoint for your site to be ready and launch. You can do it in sharepoint 2013 using content search webpart which is in content roll up category  add that webpart into your content query web part.

And if you want to display images as slider for that SharePoint add a content search webpart, this web part never shipped in earlier version of sharepoint now you can find it in webpart gallery just add it in your page where you want to display images as slider. And select its property change query and define image library and define path there. And in display template section select slide show and select item as large picture. When you finish adding webpart on your page then you will see a slider running on your SharePoint site page. But for social navigation or header you can use dreamweaver and design that area there.




Wednesday, February 24, 2016

sqlservermanagementstudio.net

SharePoint has been used for document management and been very beneficial for any organization in this domain,  Let’s elaborate a scenario to understand sharepoint 2013 document management easily -where you have multiple documents or  aspx pages pointing to single document or pdf files which could be policy file. And you received updated document from other department to update the policy document where this document is being pointed as hyperlinks to other aspx pages and within content publishing sites where content requires publishing.
If you just upload the file without doing anything then SharePoint will create new instance of that file in the same document library and you won’t be able to see changes in associated documents if its properties are not same – MS SharePoint 2013 could place space character in the file and upload that same document.
Complex scenario is when you have file hello_world.docx associated with 10 different aspx pages pointing to that file for user audience and if you receive the same updated document of that file from department to upload pdf  then you have to take great care in that – otherwise you will end up with  the smoke.
If you find this error ”file already exist” while uploading then you should rename updated file and give it a new name but don’t publish it and check content deployment job run time and within limited time you have to do this activity if your content job is setup after every 15 minutes, so if you publish it then this might be more difficult  to handle and  rename existing pdf and upload it then you have the following version
Hello_world.pdf
Hello_world1.pdf you just renamed updated pdf.
Now you can easily remove the first Hello_world.pdf and rename again uploaded pdf from Hello_world1.pdf to Hello_world.pdf and now you are done.
On the other hand you can take the backup of existing document and download existing pdf, ideally you can remove that document and just upload the updated document which you recently received with the same name.
When you will upload the same document – it should be having the same name as it was having previously or you can make changes in its property like title and name of the document that is being uploaded from property ribbon or click on column … and from there select checkout and then edit properties of that pdf.
If you just upload that document then MS  SharePoint 2013 will upload the same document inside the same document library with green mark sign- and as of now you have not published the updated document so changes will not be reflected in other associated pages that are pointing to that document with link and SharePoint will show you the old document that was already published.
If you are trying to rename that document which is updated document, and  given new name like hello_world_old.docx then trying to upload the updated document then SharePoint probably point you to the old link and rest of the aspx  pages will point to that old link not the new link and all aspx pages hyperlink will change to the hello_world_old if content deployment job has moved content and published them.
You can easily move document files or other files from one document library to another one, it will retain the entire version history you can do it with file explorer anyways but this scenario is different from the existing one.
But if you want to update the SharePoint document then remove the first one and upload the new one but first remove first one because links will be pointing to this document from other aspx pages for example and if name is changed then you won’t see it’s functioning and links pointing to that document will be changed as well.
What is advantage of this entire practice:
I don’t need to change the all hyperlink a href command in all aspx pages where this file was being pointed as a download link. If you rename this updated document and publish it mistakenly then you are gone.

Using SharePoint for document management details:

Below version history is telling me this- I have upload the same document replacing the existing one, version 1.0 and 2.0 is the old file whereas version 3.0 is newly uploaded file that has been uploaded by me with the same property title. If you can’t upload the same name file then rename it give different name upload it and remove earlier version and change this document name to the old name.
sharepoint for document management ultimate details how easily you can manage your document with it
SharePoint for document management

As conclusion just reiterating- if you want to update or replace existing document in SharePoint 2013 then just upload the document with the same property like title, description and file name as it was uploaded before for example hello_world.docx then replace it with new one hello_world.docx and SharePoint will give you green mark sign with the new one and that’s it remove the old one – if you rename the old document name then SharePoint content deployment job will move the old document to production site and all links pointing to hello_world.docx will be pointing to hello_world_old.docx. And as a result you will have to update all other apsx pages where this links has been given. So to avoid rework just remove the old document and replace it with the new one.