Introduction to Script Lab – A Simplified but powerful way to Office Extendibility

Script Lab is a Microsoft garage project which initiated with summer hackathon held back in 2016. Creator main focus is to build a platform where build add-ins simple and with less knowledge curve for web developers. It is simple but it does not mean it is not powerful. Let’s go through below slider where you could kick start on developing Office extended apps.

click here if slider does not work. 

More information
https://www.microsoft.com/en-us/garage/project-details.aspx?project=script-lab

Github Repository
http://aka.ms/scriptlab

Get Script Lab
https://aka.ms/getscriptlab – install

Office Add-ins UX design patterns
https://github.com/OfficeDev/Office-Add-in-UX-Design-Patterns

Office JS API reference
https://dev.office.com/reference/add-ins/javascript-api-for-office

Enabling External Sharing | Multidomain Sharing in SharePoint Online

In SharePoint online environment most of the businesses facing issue with connecting with another business (B2B) or in technical terms connecting with another domain.

We have been using different methods with the Active Directly level which we known as “Federation”. But will see how we could share SharePoint site with multiple domains.

📓 Note : 

  • You must have either Microsoft account or organizational account to achieve this. 
  • Microsoft account must not be Live, Outlook or Hotmail, It could be Gmail, Yahoo or another. Then you should create a Microsoft account with your domain. Eg. “example@yahoo.com”.
  • Organizational account is account in another Office 365 tenant

How to share site with external domain user?

Firstly, you must enable External Sharing in the Office 365 admin center. This could be find easily with searching external sharing in the admin center.

ext 1

Second, Go site administration and select your SharePoint site and hit on “Share” on the ribbon. Make sure and best practice 🔖 to mention your external domain you sharing as below.

ext 2

Finally added user will be visible as below in the Office 365 admin center.

📌 Some useful resources :

In memory of Office SharePoint Server 2007 aka MOSS

Naturally we all expect end on everything, same applies to software in this days. Hopefully we could not see SharePoint 2007 living with us for ten years as for now after 10th October 2017, in a way This is with the good hope on modernize and evolve with the collaboration but in a way bad news for whom love classics.

What happens after deprecation?

  • No security update further
    • This will get managing this costly
    • No patches No hot fixes from Microsoft
  • No support
    • Need to migrate to version with life as sooner
    • Not guaranteed Office365 and cloud support
  • No technical content management
    • Less documentations and resources
    • Less community engagement

Key milestones to say good bye!


“Say good bye and make your modernization plans switched on”

Improved LOOK to Office365

Since this is quick update on the Microsoft Office team and no influence on the functionality aspect, thought of make post ultra summarized. Older Office365 started rolling out in December and will continue through early 2017. Quick view will be enhanced in the home page of yours login as below.

There is a change on your apps on the cloud but more or less this is a UX (user experience) side improvements which makes Office user happy.

You can create new documents and also view latest modified documents at a glance on the home page. Documents will be simply quick preview of your OneDrive.

Your start page as can be selected on your preference with tapping on the “Settings Gear” which appears on the top right corner.

References

https://blogs.office.com/2016/12/28/the-new-office-com-gets-first-major-update/

REST and OData with Office365 APIs

When communicate with Office or SharePoint APIs, its important fact that knowledge on representational transfer protocol and OData protocols while moving with deep customization’s.

what is REST (Representational State Transfer)?

In simple terms REST is all about below;

  • Predefined set of stateless operation which identified by URL
  • Responses may contain HTML, JSON, XML or any other defined format which supported
  • GET, POST, PUT, DELETE are most common forms of HTTP verbs

rest_api

Eg.

GET:
http:///_api/web/lists/GetByTitle('Test')
GET:
https://outlook.office.com/api/v2.0/me/MailFolders/sentitems/messages/

what is OData (Open Data Protocol)?

  • Equipped with query and creational capabilities on REST APIs
  • Initiated by Microsoft in year 2007
  • Format [http or https]://<REST Endpoint URL>/<query>
http://<end point URI>?$select=value&$filter=condition$orderby=value

Open Standardization?
Standards which are developed with the involvement of community (mostly with developers). Open standards inherited to office 365 API development in following manners;
• Most of Office 365 APIs are exposed as a RESTful APIs
• Its implemented with OData 4.0 (as for year 2016)

OData queries?
OData queries is common standard which elaborated above also included in the SharePoint and Office365 end point data querying. Its ultra simple if you know the basics and played with this. Follow the following links and be expert on this.

www.odata.org : Official site for OData

graph.microsoft.io : Explore Microsoft Office365 API with queries

OData validator to validate your REST endpoints

Note : If you noticed there are versions associated with most of cloud based endpoints. Cloud services are continuously pushing changes to its services as sooner changes are ready, so then returned patterns may changed for same query. To avoid custom applications get break due to changed on endpoint, it classifies under version metadata. Simply you can pick any version which satisfies your requirement.

Querying SharePoint Endpoints as below;

SharePoint REST service query option syntax
Courtesy : msdn.microsoft.com

 

Further references