Nishant Rana

Hide Ribbon on SharePoint 2013 using CSS

Hi Guys,

I recently experienced the migration from SharePoint 2010 to 2013. I was earlier hiding Ribbon using the SPSecurityTrimmedControl and CSS. But in SP 2013 MS has divided whole ribbon in two section: s4-ribbonrow and suiteBar

Hiding the ribbon is as much as easier as it was in 2010 version. But here we just need to take care of above two mentioned sections. I have gone thorough some of the blogs where people are saying that we have change the html file(Seattle.html or oslo.html) and design manger will take care of creating master page for you (ref: Hide Ribbon).

But there is another traditional way of doing same, follow the given steps:

1) Open the master page file in the SharePoint designer.

2) Add the style tag to hide the ribbon for all the user:

#s4-ribbonrow, #suiteBar { display : none; }

3) Now we have to do…

View original post 59 more words

SLA in CRM 2015 – Part 1

There are two types of SLA available now.

Standard which was introduced in Leo and other is Enhanced.

Pause and resume features has been added to Enhanced SLA.

To enable this we need to go to Settings à Service Management à Service Configuration Settings

The pause feature is based on Status value.

In System Settings we can specify the status values on which the SLA should pause.

Let use create a new SLA

And the following SLA Item in it

SLA Item is based on First Response by KPI.

Here we can also see new Success Criteria and Success Action added to SLA.

The SLA would run if the Case Priority equals High and will wait for 5 minutes before warning and will fail after 30 minutes.

Now I go and create a new case and set its Priority as High.

The following Timer control would start running in the Case Form.

And now if I go and set the Status of Case as “Waiting for details” i.e. our pause condition.

The timer will be paused.

Now as soon as I change the Status of Case to something else

The time control will resume

Now I go and mark the case as Resolved which is our success criteria. The First response in will show Succeeded.

Hiding new item, edit, view selector from List View Web Part in SharePoint 2013

We had a requirement to hide the new item button, edit button etc. from a List View Web Part.

The way we achieved it was using a Content Editor Web Part and pointing it to Jscript File with the following CSS,

By finding the following id(s) and setting display as none.

List View with hidden controls.

Field Level Security in CRM 2015

Now supported for System (OOB) Attributes.

Contact’s “Job Title” attribute in CRM 2011

Contact’s “Job Title” attribute in CRM 2015

Can be enabled for email data type attribute

In CRM 2011

In CRM 2015

Address field are also supported.

https://www.youtube.com/watch?v=Czc9sKvWd9k

Custom Position Hierarchy in CRM 2015

To achieve the same security model that was implemented using Manager Hierarchy earlier

(https://nishantrana.me/2014/10/04/hierarchical-security-modelling-manager-hierarchy-in-crm-2015/)

in Custom Position Hierarchy we need to follow these steps.

To create Custom Position Hierarchy

Open Settings à Security à Hierarchy Security
Select Custom Position Hierarchy à Configure (Set Hierarchy Depth as 2)

Create a new position record “position 1” and add a user to it “Ceo”

Similarly create Position 2 and Position 3 record add “Manager A” and “First Name”

The Hierarchy à

Record created by user at position 3 is read only for the CEO user at Position 1 and editable for Manager User in Position 2 as we have set the depth as 2.

Hierarchical Security Modelling (Manager Hierarchy) in CRM 2015

Hierarchical Security is a new security feature introduced in CRM.

It could be either

Manager Hierarchy or Custom Position Hierarchy based.

To enable it we need to go to

Settings à Security

Let us enable Hierarchy Modelling and set the Hierarchy Depth as 2.

With depth we can specify up to what level the user can have read access to the records. Here the user will have write, update, append, append to access to those records only which are accessible to his direct report.

Let us say we have 3 users in our system.

User A, Manager A and CEO.
CEO is manager of Manager A and Manager A is manager of User A in our system.
CEO à manager à Manager A à manager à User A
User A is sales person and creates a contact record.
Now in our configuration we have set depth as 2 which means.
CEO user will have Write access to record that are accessible to Manager A and Read Access to those records accessible to User A.
CEO opens a record created by User A. ( it is read only for him)