Timeline for "Cannot find an appropriate constructor for type Microsoft.SharePoint.SPRoleAssignment" in PowerShell
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2017 at 11:51 | answer | added | kumar | timeline score: 1 | |
| Oct 24, 2017 at 17:49 | history | reopened | Mohamed El-Qassas MVP♦ | ||
| Oct 24, 2017 at 17:49 | history | edited | Mohamed El-Qassas MVP♦ | CC BY-SA 3.0 |
deleted 102 characters in body; edited tags; edited title
|
| Oct 24, 2017 at 17:10 | history | edited | NMJohns | CC BY-SA 3.0 |
added 106 characters in body
|
| Oct 24, 2017 at 17:07 | comment | added | Mohamed El-Qassas MVP♦ | Check this sharepoint.stackexchange.com/questions/147617/… | |
| Oct 24, 2017 at 17:07 | history | closed | Mohamed El-Qassas MVP♦ | Duplicate of Adding Read-Only-permissions to a list for a Sharepoint Group using Powershell CSOM | |
| Oct 24, 2017 at 17:03 | comment | added | NMJohns | I'm positive. I ran a script to verify. 2210 contains the following groups ======================== Global Read-Only QWERTY Main Members Main Owners Main Visitors | |
| Oct 24, 2017 at 16:24 | comment | added | Jim Barntish | I was able to reproduce the "Constructor not found" exception by setting $group to null. Are you sure the "Global Read-Only QWERTY" group exists? | |
| Oct 24, 2017 at 15:07 | history | asked | NMJohns | CC BY-SA 3.0 |