Am I interpreting Management OData IIS Extensions correctly? This means I can write an iOS app to run my custom enterprise PowerShell scripts?
Now I can justify iOS dev training! Cool.
Am I interpreting Management OData IIS Extensions correctly? This means I can write an iOS app to run my custom enterprise PowerShell scripts?
Now I can justify iOS dev training! Cool.
.\psexec -i -s Powershell.exe
Found this from here:
This may be a post for myself, and everyone may already know this, but I couldn’t find it quickly in a google search. I wanted to have a link to the “Week” view of a SharePoint 2010 calendar, but could not find the parmters to pass. Here they are:
?CalendarPeriod=week
?CalendarPeriod=month
?CalendarPeriod=day
And to have a specific day:
?CalendarDate=8/24/2012
About time.
About time.
Credit for this one goes to @xrobx99. He did all the work behind this post. I felt that it was such an obscure “bug”, that maybe my posting of the solution might help someone that is expereincing the same issue.
The problem we were having was that when a user would open a large PowerPoint (.pptx) file from a network share, it would always open as read-only. Looking like this :
Now, if you try and search for PowerPoint 2010 and read-only, all I can say is, good luck. You quickly get lost in “your permissions are wrong” ,and “people telling you to right click and deselect Read-only”. We had been trough all of that, and we could not lick the problem.
The symptoms we were experiencing were:
The solution that @xrobx99 figured out is that if you disable the “Preview Pane” and the “Details Pane”, the file will open correctly every time. Of course you can disable these via group policy:
User Configuration/Administrative Templates/Windows Components/Windows Explorer/Explorer Frame Pane/Turn off Details Pane And User Configuration/Administrative Templates/Windows Components/Windows Explorer/Explorer Frame Pane/Turn off Preview Pane
@xrobx99 concluded that if you leave these two panes enabled, windows explorer will open the file to generate a tumbnail, and if you double click the file during that time, it will open read-only.
Hope that helps some one.
This is the final part of these previous, posts. They setup everything (I hope) so give them a quick peak.
At this point we have the following:
Now I want to take the QueryString values and put them into the correct fields in the AttendeeList’s NewForm.aspx page (and hide these fields so the can’t be messed with) (also remember that this is all taking place in a modal dialog):
$('nobr:contains("RelatedList")').closest('tr').hide();
$('nobr:contains("RelatedItem")').closest('tr').hide();
LoopThroughQueryString()
function LoopThroughQueryString() {
var queryString = unescape(location.search);
if (!queryString) {
return {};
}
queryString = queryString.substring(1);
var pairs = queryString.split("&");
for (var i = 0; i < pairs.length; i++) {
var keyValuePair = pairs[i].split("=");
$('input[type=text][title='+ keyValuePair[0]+ ']').each(function() {
$(this).val(keyValuePair[1]);
});
}
}
Goal met. Two lists with related items. Phew that was a lot.
In Part1, I talked about how I wanted to relate items in two lists using the ID of an item in the first list. The setup for this article is here, hopefully it makes sense.
At this point, I have a MeetingList item that I am editing, and the ID of the current item is in the current QueryString. This is becasue I used this code in the previous post to redirect to this page:
window.location.href = "/Lists/MeetingsList/EditForm.aspx?ID="+ oListItem.get_id();
Now I want to add an attendee to this meeting. Here are the steps of how I went about this:
NewAttendeesRow='<tr id="NewAttendeesRow"><td nowrap="true" valign="top" width="190px" class="ms-formlabel">Add Attendees</TD><td valign="top" class="ms-formbody" width="400px"><img src="/MediaLibrary/plus_icon.gif"> Add NEW attendee</div></td></tr>';
$('nobr:contains("Meeting Subject")').closest('tr').after(NewAttendeesRow); //There is an exisitng field in the MeetingList named "Meeting Subject"
$('#NewAttendeesRow').click(function() {
ExecuteOrDelayUntilScriptLoaded(openModalDialog,"SP.js");
});
function openModalDialog() {
var options = SP.UI.$create_DialogOptions();
options.url = "/Lists/NewAtendee/NewForm.aspx?IsDlg=1&RelatedList="+_spPageContextInfo.pageListId+"&RelatedItem="+GetQueryStringParams('ID');
options.dialogReturnValueCallback = Function.createDelegate(
null, modalDialogClosedCallback);
SP.UI.ModalDialog.showModalDialog(options);
}
function GetQueryStringParams(sParam)
{
var sPageURL = window.location.search.substring(1);
var sURLVariables = sPageURL.split('&');
for (var i = 0; i < sURLVariables.length; i++)
{
var sParameterName = sURLVariables[i].split('=');
if (sParameterName[0] == sParam)
{
return sParameterName[1];
}
}
}
Part 3 will finish off my workaround.