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".
  • Blog - Mavention
    available Aangemaakt op 29 6 2015 door Albert Jan Schot Slides for the TechdaysNL 2015 available Slidedeck for Building Solutions with the Office Graph and SharePoint Shift Happens for TechdaysNL available Aangemaakt op 26 6 2015 door Albert Jan Schot Disappearing Add in Parts in Office 365 Add in parts disappearing in Office 365 Add in parts can be deleted from pages in Office 365 due to the recycle bin

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Albert-Jan+Schot%22&start=16 (2016-02-18)
    Open archived version from archive


  • Blog - Mavention
    Klanten Werken bij Contact Auteur Alle items Albert Jan Schot 116 Set a default value for PublishingStartDate An easy way to set a default value for the PublishingStartDate and PublishingExpirationDate instead of using the default today value since that leaves the value empty Aangemaakt op 29 3 2013 door Albert Jan Schot 1 21 22 23 24 Functionele SharePoint consultant Als functionele SharePoint Consultant realiseer je oplossingen voor business vraagstukken

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Albert-Jan+Schot%22&start=116 (2016-02-18)
    Open archived version from archive

  • Remove unwanted HTML attributes with PowerShell and regular expressions - Blog - Mavention
    the new website The migration scripts are being written in PowerShell so I also wanted to remove the class and style attributes with PowerShell and regular expressions It was hard to find a sample on the internet which does only remove the html attributes and not the complete elements p class mv Element P Microsoft heeft voor het derde jaar Solutions like string replace and string replace style class do not work for me as the complete elements are being removed I finally found a nice post about cleaning Word HTML with Regex in C which provided me with the correct solution for my case As my base requirement is to remove any inline styling from the HTML the extra mentioned attributes in this RegEx are also kept in my PowerShell code The working PowerShell command to clean out styling attributes from HTML elements is string replace class lang style size face ovwxp w s 1 2 Note that the dollar signs in 1 2 are escaped with back ticks to send them to the Regex processor instead as threating them as PowerShell variables Originally posted at http edwin vriethoff net 2015 09 08 remove unwanted html attributes powershell regular

    Original URL path: http://www.mavention.nl/blog/remove-unwanted-html-attributes-powershell-regular-expressions (2016-02-18)
    Open archived version from archive

  • Edwin Vriethoff - Mensen - Mavention
    het opstellen van de offerte tot en met de implementatie Edwin is integer heeft een scherp oog voor kwaliteit en weet wat klanten willen Binnen teams vormt Edwin een stabiele factor waarop men kan bouwen hij neemt initiatief motiveert mensen en laat duidelijk merken wanneer hij van mening is dat zaken verbeterd kunnen worden Hij committeert zich aan oplevering binnen begrote budget en planning want afspraak is niet voor niets

    Original URL path: http://www.mavention.nl/mavention/mensen/edwin-vriethoff (2016-02-18)
    Open archived version from archive

  • Files stored in the cloud can still be vulnerable for malware or viruses - Blog - Mavention
    sync mechanism like OneDrive for Business These techniques can be very useful but also bring the files back in reach for a possible attack Normally you should still be pretty safe as SharePoint automatically detects file changes and will generate a new version if enabled for the file Version history should allow you to revert the file back to its original state If a file got deleted by an attack you can always retrieve it back from the trash bin in Office 365 With the test I noticed one major issue filenames are not being protected by versioning If a filename change occurs the modified date is altered without an increase of the version number The version does only increase if the name changes and the content is altered at the same time but reverting back to an older version does not restore the original filename Theoretically this can be a big deal because if an attack only changes filenames to unreadable names the SharePoint library is also updated with these new filenames The user is left with an library full of unidentifiable filenames and there is no way for the user to revert back to the original names Library and version info before the filename updates Library and version info after the filename changes via WebDAV What to do if your files in Office 365 have been malformed 1 If files have been deleted navigate to the Recycle Bin to restore them back 2 If files have been altered revert back to an earlier version with version history if enabled 3 If files have been renamed you re best option is to contact Microsoft Support and ask them to do a site collection restore for you According to TechNet Data protection services are provided to prevent the loss of

    Original URL path: http://www.mavention.nl/blog/files-stored-cloud-vulnerable-malware-viruses (2016-02-18)
    Open archived version from archive

  • Create a lookup site column to a library located in a sub web with Powershell - Blog - Mavention
    a developer would be required to define the creation of the lookup column by code But with PowerShell you have a great alternative to do it with scripting and without the help of a developer However you must have desktop access to the SharePoint server The script requires you to collect a few parameters to connect with the correct list The most important thing to do is to find the correct GUIDS of the sub web and the list You can do this with PowerShell but if you aren t a developer I can recommend to use the SharePoint Manager tool This tool will help you to retrieve all required GUIDS with ease After you configured the script with your parameters paste it in a SharePoint enabled PowerShell window and it will create the lookup column for you Configuration sitecollectionUrl http sitecollection url lookupFieldWebGuid c04790db cd8a 4ab1 b9ab 9d2964a89115 lookupListGuid 5cbeb646 6517 4d8c a974 dfeca6b66672 fieldDisplayName Sample lookup fieldInternalName SampleLookup sitecolGroup Sample showField Title fieldDescription Field added by Powershell fieldHidden FALSE fieldReadonly FALSE fieldRequired FALSE unlimitedLength FALSE End of configuration siteCollection Get SPSite Identity sitecollectionUrl rootWeb siteCollection RootWeb Define lookup site colum n with a XMLString lookupXMLString Field Type Lookup

    Original URL path: http://www.mavention.nl/blog/create-lookup-site-column-different-library-subweb-from-powershell-powershell (2016-02-18)
    Open archived version from archive

  • SharePoint Ribbon customization, cui.js Invalid argument - Blog - Mavention
    having problems Chrome and Firefox performed ok After a long time of debugging randomly an internal script error was complaining about an undefined width property This clue pointed me in the right direction Our ribbon element file was adding a dropdown to the ribbon It turned out that the property width was not defined in its definition Without this information Internet Explorer will cause your customization to throw errors Keep

    Original URL path: http://www.mavention.nl/blog/SharePoint-Ribbon-customization-cui-Invalid-argument (2016-02-18)
    Open archived version from archive

  • The provided App differs from another App with the same version and product ID - Blog - Mavention
    App A first visual inspection of the SharePoint Application site indeed shows an empty application test gallery After some further investigation it turns out that the application is still visible via the Site Content overview How nice they even show a message that the app couldn t be uninstalled Luckily there is also a link to retry the uninstallation By clicking the link Click to retry SharePoint indeed initiates another

    Original URL path: http://www.mavention.nl/blog/provided-App-differs-another-App-same-version-product-ID (2016-02-18)
    Open archived version from archive



  •