meta user
network profile
| bio | website | georgedurzi.com |
|---|---|---|
| location | Chicago, IL | |
| age | 37 | |
| visits | member for | 3 years, 4 months |
| seen | Jan 8 at 14:41 | |
| stats | profile views | 45 |
|
Apr 23 |
awarded | Popular Question |
|
Feb 21 |
awarded | Notable Question |
|
Jan 14 |
awarded | Popular Question |
|
Jan 11 |
awarded | Popular Question |
|
Jan 5 |
awarded | Yearling |
|
Jan 4 |
awarded | Popular Question |
|
Dec 12 |
awarded | Popular Question |
|
Nov 5 |
awarded | Popular Question |
|
Oct 11 |
awarded | Popular Question |
|
Jun 8 |
awarded | Caucus |
|
May 15 |
awarded | Popular Question |
|
May 4 |
comment |
New site columns are not being completely propagated to a content type in a site collection tarjeieo, when I've had success using the feature upgrade process, I only specify the AddContentTypeField in the UpgradeActions. Why do you also have to update the site content type via PowerShell? |
|
May 4 |
comment |
New site columns are not being completely propagated to a content type in a site collection Steve, let me clarify about the deactivate/activate. New site columns don't appear in the site collection after upgrading the solution unless I deactivate/activate the feature that contains them. I don't expect the new columns to get added to the content type by deactivating/activating. |
|
Apr 27 |
comment |
New site columns are not being completely propagated to a content type in a site collection Found an approach that works. It's kind of stupid so I hesitate to call it answer; we found it by trial and error. Using either PowerShell or the SharePoint UI, if we add a site column to the content type, remove it, and then add it again, it propagates properly. See? Stupid. |
|
Apr 26 |
comment |
New site columns are not being completely propagated to a content type in a site collection vasya10, when I run this PowerShell on a subsite that contains pages using the content type, .Fields and .ContentTypes are empty. |
|
Apr 26 |
asked | New site columns are not being completely propagated to a content type in a site collection |
|
Mar 29 |
accepted | SharePoint 2010 search does not crawl a specific site in the site collection |
|
Mar 27 |
answered | SharePoint 2010 search does not crawl a specific site in the site collection |
|
Mar 27 |
revised |
SharePoint 2010 search does not crawl a specific site in the site collection Additional troubleshooting |
|
Mar 27 |
comment |
SharePoint 2010 search does not crawl a specific site in the site collection foocode, yes, the account does have unrestricted access. The site and its subsites is inheriting permissions from its parent (the root site) |
