How to change SharePoint List or Document Library URL using SharePoint Designer

There are two ways of changing your SharePoint list or library URL. The first one is, of course, using PowerShell which I am not going to discuss now. The second one is using SharePoint Designer. You need to have site collection admin access to do this.

Suppose you want to change the URL, http://sitename/sites/testsite/Lists/Bad List Name/  to http://sitename/sites/testsite/Lists/GoodListName/  using SharePoint Designer then follow these steps:

1.  Open your site using SharePoint Designer

2. Click All Files from left navigation menu

3. Click Lists from the list of All Files

4. Right click into Lists ->Rename and change it from Bad List Name to GoodListName.

5. This will change the URL of your list

 

That is it…

Office 365 outlook groups features comparison

Office 365 is a way that helps us use Exchange and SharePoint online together to give your teams or group of people a way to work together using the best parts of what’s available in Office 365. Office 365 groups don’t exist in the on-premises space but in hybrid deployments, Office 365 Groups can be synchronized back to on-premises Active Directory via the AAD Connect tool, where they function as distribution groups. Microsoft has made it very clear that Office 365 Groups are a cloud entity that will not appear on-premises.

Below is a comparison of outlook group features for different platforms i.e. showing the availability of the different outlook group functionalities in each client platforms:

Outlook-Groups-on-all-platforms-Sep-2015

Bulk exporting of External contacts to Office 365 Exchange online

The non-profit organization that I support uses a Google group account to host its members email address. The organization has hundreds of email addresses in this group account. As soon as the organization started using Office 365 it soon become apparent that it needed to import those email addresses into Exchange Online in bulk so that we can add these emails into a distribution group (DG) account.

How do you go about importing these external emails into Office 365 Exchange online?

  1. Go to Google Gmail account, export the email addresses and save as csv inside the c:\temp folder or wherever you like.
  2. Make sure the following fields have values inside the above-mentioned csv file:
    • ExternalEmailAddress
    • Name
    • FirstName
    • LastName
    • OtherTelephone
    • Manage
  3. Start windows PowerShell as admin and connect to your office 365 Exchange online tenant. You can connect to Office Exchange online using the below scripts. You will be asked to login and make sure you use your Office 365 admin account and password:

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic –AllowRedirection

Import-PSSession $Session

PS-email-export-01

4. Next run the following command:

Import-Csv c:\temp\ExternalContacts.csv|%{New-MailContact -Name $_.Name -DisplayName $_.Name -ExternalEmailAddress $_.ExternalEmailAddress -FirstName $_.FirstName -LastName $_.LastName}

The assumption is you saved your csv file under the folder c:\temp

As you ca see below now you should see each external users being exported to Office 365 Exchange online.

PS-email-export-02

5. Go to your Office 365 Exchange online admin center to check exported contacts

6. Click recipients from left navigation and then contacts from top tab. Now you see all your external contacts populated inside Office 365.

PS-email-export-03

Options for setting up dev environment to create SharePoint 2013 provider-hosted app

The two options that, I think, we have for creating provider-hosted apps are the following. Having said that you may have a 3rd option which is a hybrid scenario:

  1. Using a locally installed SharePoint 2013 environment (Azure or a local SP box) and configuring for a high-trust apps for SharePoint. You can have a local Sharepoint farm either by spinning an Azure VM image which has all the nuts and bolts required to setup SharePoint, AD, etc.. (this can be cheaper if you have MSDN subscriotion) or having an expensive machine where SharePoint 2013 is installed.
  2. Using Office 365 SharePoint tenant where all the configuration is setup for you via ACS – OAuth.high-trust

Here are relevant videos:

TechEd 2014 video on setting up your on-premises environment for app development.

Using an existing Windows Azure AD Tenant with Windows Azure.

Error occurred in deployment step ‘Install app for SharePoint’: SideLoading of apps is not enabled on this site

In order to publish a SharePoint hosted app to a site collection the site must be based on the developer site template or have the “Developer” Feature enabled on it.  The “Developer” Feature is marked as hidden in its definition so you must use PowerShell to enable the Feature. This error is caused when you try to deploy in a non-developer template site collection.

To avoid this error, either for SharePoint online or On-premise development, try first to create a site collection based on the Developer template and deploy your SharePoint-hosted app to this site collection. If you are deploying to a non-developer template site collection, which is something you shouldn’t be doing then here are the live links to download the SharePoint Online Management Shell i.e. for SharePoint online scenario and associated PowerShell scripts as described in the screenshot below:

side-loading

Hello world SharePoint-hosted app

As indicated in my last blog post, I am running the Apps for Office sample packs so that I can learn some their techniques. The following is what I had to do to run the “Hello world  SharePoint-hosted” app and the result I got.

  1. I run the above app by using Visual Studio 2013 update 3
  2. Below is how the file looks like under the solution explorer. Make the necessary changes as suggested below and run it.

hello-sp-hosted-app

 

3. You will immediately be asked for Office 365 user name/password and later you see the “Do you trust Basic SharePoint-hosted?” app page as follows

trus

4. Click Trust It button and you will see this result page

resultThere was some warning while I deploy the app because the CDN url for jquery as was set as http not https. Change it to https and that will take care off the error.

Another note, is that as you uninstall and install the same app the GUID for appweb  appears to remain the same except the last letter in the GUID part changing sequentially up. 

If you go to my Office 365 tenant home page, https://sharepointcan.sharepoint.com, you see a link for the new SharePoint-hosted app listed under the Recent left navigation menu as well as created within the Apps in Testing custom list. The latter custom list captures the list of apps under test as well as their appweb url.

result2

If you want to refer as to how this app is created please check the how to create a basic SharePoint-hosted app.

Now, I would like to deploy the app so that my users can start using it. How do I go about it. First make sure you deploy the app from VS 2013. Next we need to find a place where we can store the app. Options are either to SharePoint public store or your own organizational app catalog. I will create an app catalog by going into my Office 365 SharePoint Admin center. Check this how to deploying and installing apps for SharePoint: methods and options.

appcat

Go to your App catalog site collection and upload the .app file into the Apps for SharePoint document library.

app-location How to add an app

Go to any site where you would like to add this app (and a copy of the same app is not yet avilable) by clicking the gear icon a.k.a. site actions -> Add an app -> Click From Your Organization, from the left nav -> click the app -> Click Trust It button.

This will add the app into your site. When you click this newly created app, it send you to a different domain, as explained above, but same SP chrome setting.

That is it.