$graphparms = @{
appid='';
appsecret='';
aaddomain='.onmicrosoft.com';
ResourceUri='https://graph.microsoft.com';
}

Report-IaCUsageAnalytics @graphparms -ReportType OneDriveActivity -ViewType Users -Period D30 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType OneDriveActivity -ViewType Files -Period D30 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType OneDriveActivity -ViewType Detail -Date ([System.DateTime]::Parse("2017-09-06")) -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType OneDriveUsage -ViewType Account -Period D30 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType OneDriveUsage -ViewType Files -Period D30 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType OneDriveUsage -ViewType Storage -Period D30 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType OneDriveUsage -ViewType Detail -Date ([System.DateTime]::Parse("2017-09-06")) -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType SharePointActivity -ViewType Users -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType SharePointActivity -ViewType Pages -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType SharePointActivity -ViewType Files -Period D7 -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType SharePointSiteUsage -ViewType Sites -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType SharePointSiteUsage -ViewType Pages -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType SharePointSiteUsage -ViewType Storage -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType SharePointSiteUsage -ViewType Files -Period D7 -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType EmailActivity -ViewType Activity -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType EmailActivity -ViewType Users -Period D7 -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType Office365GroupsActivity -ViewType Activity -Period D7 -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType Office365ActiveUsers -ViewType Services -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType Office365ActiveUsers -ViewType Users -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType Office365ActiveUsers -ViewType Detail -Date ([System.DateTime]::Parse("2017-09-06")) -Verbose

Report-IaCUsageAnalytics @graphparms -ReportType MailboxUsage -ViewType Mailbox -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType MailboxUsage -ViewType Storage -Period D7 -Verbose
Report-IaCUsageAnalytics @graphparms -ReportType MailboxUsage -ViewType Quota -Period D7 -Verbose

• https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/Samples/script-set-customaction.ps1
  • Script Link [Inject Javascript files] https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/SampleFiles/sample-customaction-site-scriptlink.json
  • Script Block [Javascript or inject CSS] https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/SampleFiles/sample-customaction-site-scriptblock.json
  • List custom action https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/SampleFiles/sample-customaction-list.json

• https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/Samples/script-set-customaction-commandui.ps1
  • List CommandUIExtension https://github.com/pinch-perfect/Infrastructure-As-Code/blob/master/HowToExtend/SampleFiles/sample-customaction-list.xml

1. https://social.msdn.microsoft.com/Forums/en-US/bb035480-45a0-41ba-bdef-2e7cd709ce77/how-to-enable-sharepoint-designer-2013-advanced-mode-which-is-alwayes-grayed-out?forum=sharepointdevelopment  - Demonstrates the issue but doesn't tell you how to enable the feature.
2. https://blogs.msdn.microsoft.com/michael_yeager/2007/11/03/sharepoint-terms-ghosted-unghosted-and-reghosted/ - Details the difference between Ghosted and Un-ghosted.
3. https://support.microsoft.com/en-us/kb/2592376 - Outlines each setting for SharePoint Designer
4. https://github.com/OfficeDev/PnP-Guidance/blob/master/articles/SharePoint-development-and-design-tools-and-practices.md   - SharePoint design tools and practices

• strListID: typically the List GUID but we don't want to parse that out so bonus for us this also accepts the List 'Display Name',
• strListItemID: this is the unique integer value of the List item for which we will retrieve version history
• strFieldName: the Internal Name of the field

XSL:value-of  will present the current text in the field ; disable-output-escaping will handle special characters from the Rich Text fieldSharePoint:AppendOnlyHistory will present the full change history for the field, the timestamps, and editor of the change   div id="myNotesAppended" will be populated within our REST queries   div id="myNotesVersion" will be populated from scraping the HTML on the Version.aspx page

• [ODBC]
• DRIVER=SQL Server Native Client 11.0
• UID=[your username]
• DATABASE=[your database name]
• WSID=[your computer name]
• APP=Microsoft® Windows® Operating System
• SERVER=[your server name]

1. A custom web application via Entity Framework.
2. Business Connectivity Services via external content types and an external list

1. First we open PowerShell ISE (ensure you've read the prerequisites) and follow the Sample03/readme.md instructions.
2. You'll see the new list provisioned into SharePoint with the individual columns and their properties (Multi-Line, DateTime, Text) and if they are required
3. After we run the Cmd-Let to create the list we will create custom forms in SharePoint Designer
   1. I'll use the ellipse in the CEWP to browse to the Site Asset that we uploaded via the Cmd-Let
   2. I'll then remove the XSL and set the XslLink relative path to the uploaded XSL
   3. I'll go quickly over this process as it is covered in the previous post
4. We will then walk through the "new" user experience with HTML5 controls and KnockoutJs binding
5. We maintain the existing SharePoint OOTB control capability with Rich Text and markup
6. I am hiding the rich text fields and using a custom div to enable drag-n-drop
7. I keep the same PreSaveAction but in this case I place the alert in the DOM for the user to see
8. We have customized the display with additional file properties (i.e., file size included Bytes/Megabytes/Gigabytes) in the model.
9. We navigate from display to Edit and move a file from one field to another by using the custom 'Remove' command in the HTML control.
10. Watch the responsiveness of the browser as we issue asynchronous activities throughout the process.
11. If the video does not render the source file is: https://mix.office.com/watch/1chj3lxmaa387

1. First we open PowerShell ISE (ensure you've read the prerequisites) and follow the Sample02/readme.md instructions.
2. After we have run the Cmd-Let to create the list we will create custom forms.
3. First we will create custom forms for the List Actions.
   1. We copy the XSL markup from the CustomDisp.aspx page and place it in an XSL file CustomDisp.xsl in Visual Studio
   2. We copy the XSL markup from the CustomNew.aspx page and place it in an XSL file CustomNew.xsl in Visual Studio
4. We will run the Cmd-Let to upload SiteAssets
   1. We will remove the XSL markup from the CustomNew.aspx page
   2. We will then use XslLink to point the Data Form Web Part at the CustomNew.XSL file located in the Site Assets library
5. If the video does not render the source file is: https://mix.office.com/watch/bwuc6qngczko

1. First we will use Visual Studio to move the Last Updated field to the top of the XSL row
2. We will use a style=display:none for the Title field to hide it
3. We will create a div with ID to write a message to later
4. Run the Set-IaCProvisionAssets -SiteContent $RelativeOrFullPath -Verbose Cmd-Let to upload the new XSL file into the SiteAssets library.
5. Once we hit refresh in the browser we can see our changes immediately.
6. Highlight the form in the "Forms" pane and click the "Set as Default" ribbon button
7. In the video you'll see the form render as it did but we are now using the "new" custom form.
8. If the video does not render the source file is: https://mix.office.com/watch/2t5mkf31ks43

Note: In the video I use SharePoint Designer to add the webpart but I could do this in the browser if I did not have access to SPD.

1. We will open the custom form in SharePoint Designer
2. To activate the WebPart group we will need to be in a WebPart zone or somewhere in a webpart.
3. Once the WebPart group is active, insert the Content Editor Web Part
4. We will use the ribbon group to change properties of the CEWP such as the Chrome = None and 'Content Link' to the relative URL to the .html file
5. We know the path to the .html file to render JS libraries but If we didn't we could use the ellipse in the SPD 'Content Link' text box to navigate to the file.
6. Once we updated the CEWP lets make sure SPD didn't move the XslLink to a separate line (known issue)
7. Now we will hit save and navigate to the browser and hit refresh.
   1. Developer Console is opened to display the files being loaded.
   2. The DOM ready event fires setting our DIV to 'Hello World.  I've run'
8.  SharePoint list definitions can ensure field requirements and data validation.  However, there may be a variety requirements that out of the box will not meet.
9. We will extend the Sample02New.js file with a PreSaveAction() method in the JavaScript file.   SharePoint forms will listen for this function to perform pre-validation.
   1. If the field we check is not filled in then alert the user (you could use many open source JavaScript frameworks for validation)
   2. If the require field is completed, read the user input field, format it, and create a string to append to the hidden 'Title' field
10. If the video does not render the source file is: https://mix.office.com/watch/a4smzpw5qes5

1. XSD/XML schema = List Definition
2. XSL = Convert list schema to HTML via DataViewWebParts/ListViewWebParts
3. Conditional binding and controls = SharePoint web controls and jQuery