archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • SharePoint to Sitecore dictionary - Blog - Mavention
    For each component you can specify different settings amongst which parameters and the corresponding UI for editing their values Content Type Data Template The biggest difference between the two is that Data Templates in Sitecore support inheritance from multiple base Data Templates in code terms more like interfaces than base classes In Sitecore you could for example have a SEO Data Template that would contain SEO related fields and an Publishing Data Template that would contain fields like publishing start and end date By creating a new Data Template that inherits from both those templates you would have a template that allows you to optimize your item for SEO and have scheduled publishing Column Group Section No particular differences Column Field In Sitecore Fields are created always as a part of Data Template and cannot be reused across the different Data Templates You can create Fields with the same names in different Data Templates but internally they will be treated as two different fields and both will appear in the UI The only way to reuse Fields in Sitecore is through creating base Data Templates Versioning Versioning Sitecore knows two types of versioning languages similar to Variations in SharePoint and numbered versions For numbered versions Sitecore supports only major versions Drafts can be created only through workflow where draft is merely a state and not a version so no 0 1 0 2 etc Workflow Workflow Sitecore supports workflows on items At the same time an item can participate in only one workflow Each workflow has an initial and one or more final states and only items in final states are published In most common scenarios standard workflows available with Sitecore cannot be cancelled by the person who started it ie content editor who started approval process cannot cancel it

    Original URL path: http://www.mavention.nl/blog/sharepoint-sitecore-dictionary (2016-02-18)
    Open archived version from archive


  • Inconvenient recommendations for pages with Friendly URLs stored in subwebs - Blog - Mavention
    subwebs is still beneficial Subwebs and Managed Navigation better together To illustrate a challenge with using Managed Navigation with subwebs let s take a look at the following example To store press releases on your website you create a subweb called News Just as you would do in the past you use News for the title of the subweb and news for its URL To test if things work as expected you create a menu item for the news landing page in the Managed Navigation The Friendly URL is set to news and the target page for the Navigation Term points to the Welcome Page of the News subweb news Pages default aspx This all seems to be configured correctly and if you now try to navigate to News you will see the landing page of the News subweb If you however try to create a press release with a Friendly URL in the News subweb you will get a Page not found error when you try to navigate to it This has to do with the fact that both the Friendly URL of News and the URL of the News subweb are called news and where trying to locate the template page SharePoint doesn t know how to retrieve it This issue can be easily fixed by changing the URL of the News subweb to something else like news note the trailing underscore Even though it isn t pretty it isn t a problem at all since all your visitors will see is the Friendly URL To confirm that everything works just as expected you can check the Search Analytics log and see that the correct Friendly URL of the press release page is logged Inconvenient Friendly URL of pages stored in subwebs in search queries Having verified that the visits to our pages are logged correctly the next step is to retrieve content recommendations This can be done easily using the standard Recommended Items Web Part Unfortunately if you add this Web Part to the press release page you will see no recommendations There might be many reasons for why no recommendations are retrieved but if you take a closer look at the URL used to find recommendations for you will see that it s different than the URL of the press release page By default the Recommended Items Web Part uses the Page query variable to get the URL of the current page Unfortunately this variable resolves to the absolute URL of the current web plus the URL of the page as defined in Managed Navigation As you can imagine this URL is not a valid URL and different than the actual Friendly URL of the page As a result no recommendations will ever be found Although SharePoint 2013 Search offers a number of query variables to return the URL of the current page none of them returns a valid absolute URL for a page with Friendly URL stored in a subweb that could be used to

    Original URL path: http://www.mavention.nl/blog/inconvenient-recommendations-pages-friendly-urls-subwebs (2016-02-18)
    Open archived version from archive

  • Easy inserting symbols in SharePoint 2010 with Mavention Insert Symbol - Blog - Mavention
    a copyright or a trademark sign in content If you are editing content directly in SharePoint there is no easy way for you to insert such symbol You have to copy the symbol from another place and paste it in SharePoint If this scenario sounds familiar to you then the Mavention Insert Symbol solution is just the right thing for you Find out how to insert symbols in content in SharePoint 2010 the easy way with Mavention Insert Symbol Mavention Insert Symbol is a Sandboxed Solution for SharePoint 2010 Upon activation of the Solution a new Site Collection Feature is installed After you activate the Feature the Insert Symbol button will be installed on the Ribbon Whenever you re editing content and need to insert a symbol all you have to do is to click the Insert tab go to the Content group click the Symbol button and choose your symbol After you click on a symbol it will be inserted at your cursor Download Mavention Insert Symbol 5KB WSP Originally posted at http blog mastykarz nl easy inserting symbols sharepoint 2010 mavention insert symbol IE7 fixes in SharePoint I just found out not to use conditional comments for IE

    Original URL path: http://www.mavention.nl/blog/easy-inserting-symbols-sharepoint-2010-mavention-insert-symbol (2016-02-18)
    Open archived version from archive

  • Inconvenient Search REST API for anonymous users - Blog - Mavention
    and you are getting some search results the odds are high that those results are different than the results that you should be getting So what is wrong exactly Inconvenient Search REST API for anonymous users It turns out that when building the configuration file for anonymous access to the Search REST API if there is a mismatch in the Site Collection or Web ID SharePoint 2013 Search will fall back to the default Result Source Tip When building the configuration file for anonymous access to the Search REST API you can leave the Farm ID configured as an empty GUID This is very useful for configuring access to the Search REST API for users with restricted read permissions in Office 365 who also require the same configuration as anonymous users and where there is no way for you to get a hold of the Farm ID What s inconvenient about this situation is that unless you thoroughly verify the query results and compare the source ID to the one you used in the query SharePoint 2013 won t return any error if there is a mismatch in the configuration file and it might not be obvious at first that you re getting results other than requested The good news is that it can be fixed fairly easy by including the correct Site Collection and Web ID s in the configuration file Changes to the query results should be seen immediately Summary SharePoint 2013 allows you to use its Search REST API with both authenticated and anonymous users In order to use the API with anonymous users though some additional configuration steps are needed If this configuration is done improperly you won t see any errors Instead you will see SharePoint using the default Result Source instead the one requested

    Original URL path: http://www.mavention.nl/blog/inconvenient-search-rest-api-anonymous-users (2016-02-18)
    Open archived version from archive

  • Inconvenient programmatically working with Managed Navigation and anonymous users - Blog - Mavention
    to the SiteMap Provider either the default one using the SiteMap Provider property or a specific one requested from the SiteMap Providers collection After that you can retrieve the navigation nodes either by starting from the RootNode or the CurrentNode property The returned nodes are of type SiteMapNode but they can be casted to the TaxonomySiteMapNode type to give you access to the specific capabilities of Managed Navigation Following is a simple code snippet that illustrates programmatically working with Managed Navigation SiteMapProvider provider SiteMap Provider SiteMapNode currentNode provider CurrentNode TaxonomySiteMapNode taxonomyNode TaxonomySiteMapNode currentNode So far everything works just as expected What if however we wanted to get access to the underlying Term to read some of the custom properties it had configured To do that we could use the following lines of code TaxonomySession taxonomySession new TaxonomySession SPContext Current Site string myProperty null if taxonomyNode NavigationTerm GetAsEditable taxonomySession GetTaxonomyTerm LocalCustomProperties TryGetValue MyProperty out myProperty do something with the property value else property not set Using the NavigationTerm property we first get access to the underlying Navigation Term Before we however will be able to access custom properties set on the underlying Taxonomy Term we need to convert it to an editable Navigation Term using the GetAsEditable TaxonomySession method With this we are now able to access the underlying Taxonomy Term by calling the GetTaxonomyTerm method That gives us access to the Term object from which we can access the LocalCustomProperties property that contains all custom properties set on that Term The code snippet presented above will work just fine unless the page is requested by an anonymous user Inconvenient programmatically working with Managed Navigation and anonymous users If you try to execute the code snippet presented above as an anonymous user you will get an InvalidOperationException with the Term not found message The reason for this error is the fact that by default anonymous users are not allowed to get Navigation Term as Editable Navigation Terms So what are the available options to solve this issue Option 1 elevate permissions The first thing that you could consider is elevating permissions for the purpose of this code snippet This is a common solution to all kinds of permission related issues with anonymous users in SharePoint Following is how the code snippet would look like Guid siteId SPContext Current Site ID SPSecurity RunWithElevatedPrivileges using SPSite site new SPSite siteId TaxonomySession taxonomySession new TaxonomySession site string myProperty null if taxonomyNode NavigationTerm GetAsEditable taxonomySession GetTaxonomyTerm LocalCustomProperties TryGetValue MyProperty out myProperty do something with the property value else property not set While this code would without a doubt do the job and work as expected it s quite resource expensive to instantiate a new reference to SPSite each time you need to process a Navigation Term And while you could keep the SPSite reference and reuse it for processing multiple Terms or apply some other kind of optimizations it is still far from ideal Luckily there is a less intrusive way to solve the problem

    Original URL path: http://www.mavention.nl/blog/inconvenient-programmatically-working-managed-navigation-anonymous-users (2016-02-18)
    Open archived version from archive

  • Nieuws - Mavention
    Amy van der Spek Mavention hoofdsponsor Intranetcongres 2015 Wilt u weten hoe u uw intranet of digitale werkomgeving kunt verbeteren Op het Intranetcongres 2015 leert u hoe Mavention en andere organisaties dit hebben aangepakt Aangemaakt op 13 2 2015 door Amy van der Spek Albert Jan Schot MVP spreekt 28 januari op DIWUG event Hoe kunt u Office Graph eenvoudig inzetten in uw apps Woensdag 28 januari laat Albert Jan

    Original URL path: http://www.mavention.nl/nieuws?toggleRwd=0&start=21 (2016-02-18)
    Open archived version from archive

  • CSOM chain includes to retrieve all labels for all terms - Blog - Mavention
    load you will include only the default properties Using the Include you can easily identify that you would like to load a termset and all it child terms Web ctxWeb context Web context Load ctxWeb w w Language context ExecuteQuery TaxonomySession taxonomySession TaxonomySession GetTaxonomySession context TermSetCollection termset taxonomySession GetTermSetsByName sampletermset int ctxWeb Language context Load termset termSetsArg termSetsArg Include termSetArg termSetArg Terms context ExecuteQuery However you can chain these Include methods as well So instead executequery multiple times you can create a single load and chain the includes So that with a single execution you can retrieve everything you require To do so you can use the same include as before but add an extra argument with another include In that second include you can specify what properties you require for that object As you can see in the following snippet it is fairly easy Web ctxWeb context Web context Load ctxWeb w w Language context ExecuteQuery TaxonomySession taxonomySession TaxonomySession GetTaxonomySession context TermSetCollection termset taxonomySession GetTermSetsByName sampletermset int ctxWeb Language context Load termset termSetsArg termSetsArg Include termSetArg termSetArg Terms termSetArg termSetArg Terms Include t t Labels context ExecuteQuery if termset null termset Count 0 ts termset 0 I was a

    Original URL path: http://www.mavention.nl/blog/csom-chain-includes-retrieve-labels-terms (2016-02-18)
    Open archived version from archive

  • Inspirerend Intranetcongres 2015 - Nieuws - Mavention
    Floreveld Hoe faciliteert Floreveld een slimmere communicatie kennisdeling en samenwerking binnen de 30 basisscholen van Flore Wouter Geurtzen van Mavention lichtte de techniek achter dit eenvoudig te beheren intranet toe met als basis Microsoft Office 365 De toehoorders waren vooral benieuwd naar wat het Stichting Flore heeft opgeleverd en of het samenbrengen van de 30 scholen op één intranet tot weerstand leidde Na de presentatie werd in de Mavention stand nog nagepraat over de faciliterende rol van Floreveld om makkelijker te kunnen samenwerken En het belang van het menselijke aspect wil een implementatie slagen Veranderingen door technologie Het begin en de afsluiting van de dag werd verzorgd door 4 gerenommeerde sprekers Zij spraken over onderwerpen als de kracht van een netwerkorganisatie het belang van leiderschap in een digitale werkomgeving en change management om social business mogelijk te maken Ze schetsen een beeld van de veranderingen in ons leven door de snel groeiende technologie Zoals de Zweedse jongen PewDiepie die inmiddels miljoenen verdiend met zijn YouTube video s waarin hij onder andere videogames speelt en becommentarieert Met 3D printen wordt straks iedereen zijn eigen producent En door de ontwikkeling van de zelfrijdende auto s halen onze kinderen misschien nooit een rijbewijs

    Original URL path: http://www.mavention.nl/nieuws/inspirerend-intranetcongres-2015 (2016-02-18)
    Open archived version from archive



  •