User Profile
paulpascha
Bronze Contributor
Joined Jul 16, 2016
User Widgets
Recent Discussions
Content Type Gallery current state and experiences
Hi all, In the past I've seen several customers making use of SharePoint's "Content Type Hub" where over time these customers started running into issues related to using this service. For example, over time creating new sites in the environment started to take longer and longer... Recently the Managed Metadata service was modernized and "Content Type Hub" was renamed to "Content Type Gallery". I am wondering about experiences nowadays around the usage of this service. Can we consider this service mature and stable, also in larger-scale scenarios? Little background: we're currently planning our migration to SharePoint Online and we're wondering if we should reconsider making use of the Content Type Gallery. Alternatively we will create the same set of columns and content types through our own automated process like we were used to. Thanks!791Views0likes1CommentRead configuration information from Search and User Profile Service Applications using remote API's
Hi all, We're currently in the process of implementing a solution for comparing differences in SharePoint configuration across our DTAP environment. We want to compare configuration settings across sites, but also in service applications like User Profile Service (i.e. custom properties and their settings) and Search (i.e. managed property configurations). Our environment is SharePoint 2013 on-premises but we prefer to make use of remote API's (REST / Managed CSOM) to read these kinds of configuration information. So far I didn't discover any Remote API that could help us get the information we need. Can anyone here point me to such API's or confirm my guess such remote API's just don't exist and we would only be able to user Server-side API's?607Views0likes0CommentsRe: Deleted Content Type Reappearing
Before deleting a Published Content Type from your Content Type Hub you should Unpublish it to prevent it from being recreated the next time the Content Types are syndicated by a background process (Timer Job). The blog below explains the above in more detail: https://www.contentprecedesdesign.net/2014/06/sharepoint-content-type-publishing-delete-vs-unpublish.html1.6KViews0likes1CommentRe: How to debug custom SharePoint Web Service
Besides modifying your web.config you'd have to attach your debugger to the W3WP (IIS) worker process. You can do so from within Visual Studio --> Debug --> Attach to process. There is probably more than 1 instance of this process running. You could attach to all of them or figure out the correct one by following the steps detailed in below blog: https://www.sharepointpals.com/post/how-to-identify-and-attach-correct-w3wp-process-in-visual-studio-while-debugging Hope this helps2.1KViews0likes0CommentsRe: Save as template again!!!
This is an error related to a Calculated Field in your template. As the error says it refers to a column that doesn't exist. You should check the name of your column and make sure it exists before your calculated field is created. Does this make sense?2.2KViews0likes0CommentsRe: Content and Structure capability to move sites
Not really an elegant solution, not my recommendation and probably not supported anymore but the page is still available if you know it's URL. You can get there by appending below URL to your site URL: /_layouts/15/sitemanager.aspx?Source={WebUrl}_layouts/15/settings.aspx You could test if this page still works for you. Alternatively, without making use of 3rd party solutions, you would end up using Microsoft's own SharePoint Migration Tool optionally combined with some custom development I guess. I think it's safe to assume this Feature will not return. Given the fact that creating a flat hierarchy of Site Collections subscribed to Hub Sites is (justly) considered a better approach over creating sub sites.1.2KViews1like0CommentsRe: Customize your term set is disabled why
This option creates a new Term Set that's only available for use in the Site Collection you're currently in, also known as a "Local Term Set". This is useful in scenario's where you want to use the benefits of Managed Metadata Columns and Term Sets, but when the terms in the Term Set only apply in the context of your current Site Collection instead of tenant-wide/company-wide. In your case it's probably disabled because a lack of permissions assigned to you. Only site collection administrators can create these Local Term Sets.1.6KViews0likes0CommentsRe: Transition existing intranet to Hub sites
Microsoft also provides a migration tool which could be good enough for the job at hand and free to use, you can start evaluating this tool : https://docs.microsoft.com/en-us/sharepointmigration/introducing-the-sharepoint-migration-tool2.7KViews1like1CommentRe: Migrate SharePoint 2010 to 2016
Both Workflow (SP2010 and SP2013) and InfoPath are still supported to be used in combination with SharePoint 2016. See below blog for official statement on this (under Frequently Asked Questions): https://www.microsoft.com/en-us/microsoft-365/blog/2016/01/20/sharepoint-server-2016-and-project-server-2016-release-candidate-available Aside from official support, you should start thinking about the future taking Microsoft's roadmap and announced deprecations into account. If your future is on-premises there are no real alternatives other than 3rd-party solutions or custom development. If you are considering moving to SharePoint Online, you'll see that workflow scenarios can be implemented by using "Microsoft Flow" and PowerApps is generally considered (and positioned by Microsoft) to be the InfoPath replacement.1.2KViews0likes0CommentsRe: Why cant i export the column "version" from my sharepoint library to Excel?
I don't know the exact reason but this default behavior is "By Design". In that sense nothing is going wrong and you're not doing anything wrong. As a workaround, you could add a Calculated Column to your library with formula "=Version". If you include this calculated column in the view from which you're exporting it will be included in your Excel export Hope this helps1.5KViews0likes0CommentsRe: Transition existing intranet to Hub sites
Office 365 / SharePoint Online provides no built-in ways for you to promote sub-sites to site collections. I think the best migration approach is to design your new structure based on site collections and hub sites and then migrate relevant content to its new place within your redesigned structure. This also gives you the opportunity to cleanup / remove possibly outdated content. You will probably end up using a 3rd-party migration tool for this such as ShareGate.2.7KViews2likes3CommentsRe: SharePoint Online - classic configuration or not?
I think using the modern experience for green field scenarios should be your primary goal. Many of the structures / functions from classic experience are still there or have an equivalent that provides similar functionality. In general, deprecated functionality (once officially announced) will stay in SharePoint and supported by Microsoft for quite a long time. I don't see any movement in the basic structures of Fields, Content Types, Taxonomy, Lists and Libraries. I think it's safe to build your solution around these for the foreseeable future. There are many things in SharePoint Online still available that have a better, modern alternative. We shouldn't use these anymore in greenfield scenarios and we should plan to replace them in brownfield scenarios. For example I wouldn't design new solutions anymore that incorporate Workflow (2010/2013), InfoPath, BCS, Content Organizer, etc...1.4KViews2likes0CommentsRe: Cross site lookup
This scenario, in the way it worked in your SharePoint 2013 environment with subsites, still works exactly the same in SharePoint Online and is also supported. Perhaps you should consider moving to more modern site structure using multiple site collections and hub sites but that's another topic. "Cross site" typically refers to the use of multiple site collections. Having lookups across site collections is not supported out of the box.5KViews0likes0CommentsRe: How correctly store list
Ultimately it all depends on what kind of content you need to store in your site required to support the process your site is used for. If more than 10 lists are required to support your process or goal, it's fine to create them. In the end you have to think about how to expose the data that resides in your lists to the end users of your site in an easy to use and friendly way, usually this means planning for separate page's with WebParts to expose your list data on your site and providing a well designed search-experience. If you're concerned about the number of lists in your site growing too big you can consider creating additional SharePoint sites or Groups and optionally relate them to each other by subscribing them to one or more Hub sites620Views0likes0CommentsRe: Exception calling "ExecuteQuery" with "0" argument(s): "The node to be inserted is from a different
Could you try to see what happens if you separate the changes of SetShowInEditForm and SetShowInNewForm? Changing your code as follows: $customfield.SetShowInEditForm($true) $customfield.UpdateAndPushChanges($true) $Context.ExecuteQuery() $customfield.SetShowInNewForm($false) $customfield.UpdateAndPushChanges($true) $Context.ExecuteQuery()13KViews0likes2Comments
Recent Blog Articles
No content to show