Showing posts with label Sharepoint 2013. Show all posts
Showing posts with label Sharepoint 2013. Show all posts

Wednesday, April 3, 2013

Office 365 - Site MailBox in replacement to Document Library incoming Mail?

I have to say that I have underestimated the site MailBox feature of Office 365.

As explained on the blog of Benoit Hamet http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=484,this feature gives a lot of new capabilities, but it comes with its lot of missing features!

After having activating the web scoped feature "Site Mail Box", I have first been surprised in a wrong way by this feature :

It creates an exchange mail box that can be accessed via the interface and where all the members of your site can pick documents and mails. Isn't it great that only by activating a feature it creates you a exchange mail box for your site? After the excitment, come the questions..
With my local Sharepoint 2007-2010-2013 I can configure my library to receive emails and to store documents. With some mix of Rules/workflows/taxonomy/Item receivers I can even create a string redirection system. can I do that with MailBox? apparently no...
Apparently!

I have then configure my Outlook 2013 in order to get my personal Office365 emails offline. And looking inside the menus (I'm curious) I have found this item "Manage All site mailboxes" on the contextual menu of my personal mailbox. (sorry if I don't put screenshots, but mine is in french!)

The first time I clicked on it, nothing was displayed. The basic reason is that office 365 tries to see whether you are in the member/owner group of the site and if not it doesn't provide you the access to the mailbox (even if you are farm admin like I was). Second Try after having added me in the site owner group. The mail box is displayed and it comes up inside outlook with all the document libraries of the site!

You can apply outlook rules on this mail box! So basically, I can redirect whatever I want using those rules!

Play well!

Other sources :
http://blogs.technet.com/b/exchange/archive/2012/08/22/site-mailboxes-in-the-new-office.aspx
or/and (french)
http://spasipe.wordpress.com/2013/03/07/sharepoint-2013-les-site-mailboxes-14-configuration/
 

Monday, March 25, 2013

Create a new Community Template - Discussion/category Product bug

I'm actually working on a office 365 Social network project. Really interesting by the way.
I just lost two days believing that I had done something bad when I found on my newly created community (and actually all others) that the discussion board weren't linked correctly to my discussion board categories. Note that my community  template is not the basic one but a slightly customised one...

So, I have started everything again...  and again the same mistake...

So, I have tried a really basic test : I did the same test with the standard community template and I expected it to work, but there is the same problem with the standard template!
I tested it as well on my local environment the problem is exactly the same.Let's correct it!


  1. Open you newly created category.aspx page
  2. Open the two problematic webpart's property panel
  3. Change the view :
    1. for the proposed discussion webpart, set it to "Proposed discussion"
    2. for the other one, set it to "subject"
  4. From now, once you validate your page, you will have everything almost working, the only left problem is that you don't see the discussions according to the category of the page. let's continue.
  5. Open two instances of Sharepoint Designer 2013. One on the source site, and one on the target site. On both open category.aspx page
  6. On the target page, in all the xsltlistviewwebpart's parameterbinding, there is binding missing, you have to add it! 
  7. Almost at the end of page of your source page, locate the {CategoryID}, you will have to place it exactly at the same place on your target page.
  8. Save it.
  9. Test it & pray !


Friday, November 9, 2012

Sharepoint 2013 Newsfeed Vs Office 365 newsfeed

You have liked the newsfeed of Office 365 giving the capability to display videos and images directly on the newsfeed... Your enthousiasm will fall down when you open the newsfeed of Sharepoint 2013...

The videos and photos display simply disappears.

So far, the problem has been mentionned several times on posts
http://community.office365.com/en-us/preview/forums/717/p/72621/273783.aspx
or
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/1c57452a-12c0-4e11-aa59-f3bc7900d7a7

UPDATE : 14/11/2012
My mistake (I don't erase the current post because the mistake can have been done by others) !!

In fact on the communities sites, the discussion list created as default on the community sites is not displayed on the Office 365 community site. On those sites the site collection feature "Site Feed" is activated and it is the newsfeed that is displayed as main page. There you have the preview displayed and you can embbed photos and videos!








Sharepoint 2013 - Add Geolocation Field in the display view of a discussion List

Imagine the scenario : You 'are on a community, you want to be able to post your position on a post to show the other users your localization. (FB like).

The idea WOULD be :
  • Add a geolocation field
  • Add the field to the display
  • TADAAM it works...
Well obviously, it doesn't!

The method is a bit more complicated. We've worked on it with Laurent Fauret (also from Sogeti) who made the js updates :

Step 1 : Create a site Column Geolocation field
The geolocation fields can't be created manually. So you have to create them using A powershell script or Using Create Geolocation field projet on Code.msdn.microsoft. Add a field in yor discussion list.

Step 2 : Update the discussion display file
The problem is that you never open the viewItems.aspx form when you navigate inside a discussion, you are always on a custom view, so the field you have added on your list, will never show up! So, it means that you have to modify the display js file!

This is not a good way of doing but it's a fast one! You should never touch the standard file of sharepoint, but instead create your owns specific but in this case we will do it for demo purpose (the good way would be to create a discussion list type based on the new display js file!)

So you have to modify the sp.ui.discussions.js located in the 15/TEMPLATE/Layouts. It manages the display of the discussion list. (use the sp.ui.discussions.debug.js to have the indented version).

  • Add your field in the viewfields list in the function
     SP.UI.Discussions.Helpers.$1f = function (m, i) 
  • Change the $2u_0: function (a, d)  to
     $2u_0: function (a, d) {
        ULS06I:;
        this.populateFolderMetalineItems(d);
        a.addCssClass("ms-comm-metalineList ms-noList");

        a.renderBeginTag("ul");
        if (this.jsonItem["My_x0020_Location"]) {
            a.addCssClass("ms-comm-metalineItemSeparator");
            a.addCssClass("ms-comm-metalineItem");
            a.renderBeginTag("li");
            a.write(spMgr.RenderFieldByName(this.$0_0, "My_x0020_Location", this.jsonItem, this.$0_0.ListSchema))
            a.renderEndTag()
        }
        for (var b = 0, c = this.$R_0.length; b < c; b++) {
            b !== c - 1 && a.addCssClass("ms-comm-metalineItemSeparator");
            a.addCssClass("ms-comm-metalineItem");
            a.renderBeginTag("li");
            a.write(this.$R_0[b]);
            a.renderEndTag()
        }
        a.renderEndTag()

    },

  • Change the $2y_0: function (a) { to$2y_0: function (a) {
            ULS06I:;
            var loc = spMgr.RenderFieldByName(this.$0_0, "My_x0020_Location", this.jsonItem, this.$0_0.ListSchema);
            if (loc) {
                a.addCssClass("ms-metadata");
                a.addCssClass("ms-comm-cmdSpaceListItem");
                a.renderBeginTag("span");
                a.write(loc);
                a.renderEndTag();
            }
        a.addCssClass("ms-metadata");
        a.addCssClass("ms-comm-cmdSpaceListItem");
        a.renderBeginTag("span");
        var b = spMgr.RenderFieldByName(this.$0_0, "Created", this.jsonItem, this.$0_0.ListSchema);
        a.write(b);
        a.renderEndTag()
    },



Note :We have called our column "My Location".



Step 3 : Test
It works only on your /discussion%20List/forms/allitems.aspx ... but it f you want to see it working on your site homepage (where the discussion list is already put), you have to revalidate the "subject" view on the discussion list Webpart for the view to be updated with your new field.
An now you will see your GeoLoc picto on your discussion!


And on the click



Thursday, October 25, 2012

Can't add an oinline Apps on your newly created Sharepoint 2013 farm?

So excited with my new toy...
I have found on the Office online app store (http://office.microsoft.com/en-us/store/apps-for-sharepoint-FX102804987.aspx) a Chat app that I wanted to add.

So, on my newly created site, I went to Add an app, I tried to reach my store (easy!) but once arrived on the page of my desired app, I found an unpleasant message "App are not allowed on your Server ...blablablabla..."

After having tried to activate some services manually, trying to reach the "configure App URL",  I checked online and finally found this :
http://sharepointchick.com/archive/2012/07/29/setting-up-your-app-domain-for-sharepoint-2013.aspx
and I finally went there :
http://msdn.microsoft.com/en-us/library/fp179923(v=office.15)

I performed all the steps mentionned on the msdn. It simply worked! So. Forget the easy configuration of SP 2010.

Now you have to create your app store using your powershell interface!

Wednesday, October 24, 2012

Sharepoint 2013 RTM for MSDN Subscribers!

We are actually working on the Enterprise Social Network of a big company. We plan the migration on Sharepoint 2013. So I was about to test the migration  using the RC (Waiting for the RTM then...)

Today, I was looking on my MSDN (ultimate) Account, to retrieve the product key for the RC version... the one I found on the MSDN didn't work on my installation... WHY doing that to me?

simply because today... the version changed to RTM (also did Office 2013!) and so: new product = new Key!

YEAAAHHH :)