meta user
network profile
| bio | website | derekgusoff.wordpress.com |
|---|---|---|
| location | Michigan | |
| age | ||
| visits | member for | 1 year |
| seen | 20 hours ago | |
| stats | profile views | 43 |
|
May 15 |
comment |
Dynamically registering JavaScript from within a sandbox web part sorry to have wasted your time. I'm glad you found a solution. |
|
May 8 |
answered | missing content type name and description in the new item dropdown |
|
May 2 |
comment |
Hide fields on NewForm.aspx and EditForm.aspx based on the current user's membership in a SharePoint Group if that's outside your abilities you'll have to use alerts everywhere. |
|
May 2 |
comment |
Hide fields on NewForm.aspx and EditForm.aspx based on the current user's membership in a SharePoint Group You'll need some debugging to sort this out. Unfortunately your options for debugging in a CEWP are limited. By now you know the ready() handler is firing, so then you'll need to figure out: 1) did the SPServices call succeed, 2) did the XML contain what you expected, 3) was the group you were searching for found, 4) was hidefields() called, and 5) did the jQuery in hidefields() actually find the field. If it were me I'd ditch the CEWP and just write the javascript onto the page using SPD, and step through the code using F12, and possibly Fiddle the SPServices call. |
|
May 1 |
comment |
Hide fields on NewForm.aspx and EditForm.aspx based on the current user's membership in a SharePoint Group Keep in mind that if you need real security (i.e., this is sensitive data), this is not the way to do it. A savvy user will find a way to "unhide" this hidden field. |
|
May 1 |
answered | Hide fields on NewForm.aspx and EditForm.aspx based on the current user's membership in a SharePoint Group |
|
Apr 29 |
answered | Event Receiver site creation |
|
Apr 26 |
comment |
Moving SharePoint portal to ASP.NET web application on the bright side, when you are finished you will make millions selling it! |
|
Apr 26 |
comment |
Lookup field two projects also, forget about Project 2 for the time being, and deploy project 1 to a fresh site, and verify the lookup works in site settings -> site columns. Once you get that consistently working (on one deployment), go ahead and deploy project 2. |
|
Apr 26 |
answered | Lookup field two projects |
|
Apr 26 |
awarded | Yearling |
|
Apr 26 |
answered | Lookup Field programmatically in FeatureActivated |
|
Apr 21 |
answered | Source control mechanism in SharePoint designer 2010 |
|
Apr 21 |
answered | Is availability of port 80 a must for a SharePoint? |
|
Apr 14 |
answered | Best practice for deploying Site Columns and Content Type |
|
Apr 5 |
comment |
which is better building sites/libraries through Ul or programmatically? Agreed, you are virtually guaranteed to have errors doing all this work by hand. In the time it would take to build the lists by hand, you could programmatically create them in a QA environment and do a week of testing on them. |
|
Mar 29 |
answered | Where I can use asp.net MVC with my SharePoint 2013 project |
|
Mar 26 |
comment |
ListData.svc REST and URL Encoding of Field 'Parts Released?' +1 for proactively handling the internal name question! |
|
Mar 22 |
comment |
ASMX service returns only part of the list items, not all of existing items done, and thanks! |
|
Mar 22 |
answered | ASMX service returns only part of the list items, not all of existing items |
