CalendarExtender initially appears blank

This is a recent issue that I have in which I have a "Issue Tracking" List that maintains the workflow of contract renewals.

When an person goes to edit an existing list entry, the description field (standard) has the original text in the box. Prior to this the original - or any older text from a prior change was listed outside and just below the box - and non editable.

That's not the case anylonger.

Any thoughts?

Regards

Andy

Hi,

I'm about to go NUTS :)

I have 2 CalendarExtenders on page. And I want to show the date that I get from SQL SEVER:

select -> SELECT convert(datetime,  begin) as Begin, convert(datetime, end) as End FROM Table

The date field, on base,  is a char(8)  and the record is like YYYYMMDD. That's why I convert it to datetime.

But, on code behind when I do this :

CalendarExtender1.SelectedDate = DateTime.Parse(objDataEvento.Rows(0)(2))
CalendarExtender2.SelectedDate = DateTime.Parse(objDataEvento.Rows(0)(3)) 

Depend of the date, It's showing minus 1 day on page.

Like: If, on base, the date is 08/12/2010, on page it's showing 07/12/2010.

WHYYYYYYYYYYYY ???????????????  

 

 

 

Hi,

We are having an issue with occasional Tasks being created by a WF that have a blank Assigned to field.  Solution consists of:

1. A form with a People picker field that allows the user to select and validate the Authoriser name.
2. An Auto-start-on-New SP Designer workflow runs that does a "Collect Data from User action" and assigns the Task to the Authoriser.

Unfortunately, although this worked fine during dev and test, now the solution is live and we are having 150-200 requests per day, we are finding that the WF occasionally fails to fill in the Assigned To details when it creates the Task. (approx 8 failures per 200 requests, ie 4%).

As SharePoint already has the User data field, I am confused why this might fail, and there is no obvious pattern (same auth, 4 work OK then 1 failure). 
Does SP contact the AD again when it creates the Task?

Anything else I should investigate? any suggested fix / work-arounds?

Ruth

Hello,

I have implemented a custom ModelMetadataProvider so that I can decorate my view models with some custom attributes and everything was working fine until I made use of a Partial View.

The following code in my view works fine: -

<%: Html.DisplayFor(x => x.Results) %>

Results is a List which renders a custom display template and is also decorated with a custom attribute.  Using breakpoints, after the above line and prior to the code within the custom display template, the overridden CreateMetadata method in my custom ModelMetadataProvider is invoked.  If I look at the attributes collection parameter I can see that it does contain my custom attribute thus everything working as expected.

However, if I replace the above with the following line of code in my view then it breaks: -

<% Html.RenderPartial("ApplicationSearchResults", Model.Results, new ViewDataDictionary()); %>

All the Partial View contains is: -

<%: Html.DisplayFor(x => x) %>

Again using breakpoints, after the above line and prior to the code within the custom display template, the overridden CreateMetadata method in my custom ModelMetadataProvider is invoked.  But this time if I look at the attributes collection parameter my custom attribute is not there.

Any idea