Re: Appointments error after CRM 4.0 upgrade. by Jevgenij
Jevgenij
Fri Dec 28 22:33:26 CST 2007
Hello!
I would recomend to open a support case with Microsoft - this could be a bug
of CRM 4.0 and could be fixed,
but if you don't have time to wait and are ready to take a risk of
unsupported path, your option here is to make a direct DB edit.
Here is the query:
------------
UPDATE MetadataSchema.Attribute
SET AttributeLogicalTypeId = 'duration'
WHERE MetadataSchema.Attribute.AttributeId =
(
SELECT MetadataSchema.Attribute.AttributeId
FROM MetadataSchema.Attribute INNER JOIN
MetadataSchema.Entity ON
MetadataSchema.Attribute.EntityId = MetadataSchema.Entity.EntityId
WHERE (MetadataSchema.Attribute.Name = 'actualdurationminutes' AND
MetadataSchema.Entity.ObjectTypeCode = 4201)
)
------------
Please note, that this is fully unsupported and you should definitly make a
backup before running the query.
Also, thorough system testing should be done after the change.
I can't guaranty this won't break something or even work, but I hope this
helps.
Good Luck and Happy New Year,
Jevgenij
<lux186@gmail.com> wrote in message
news:ef5f9667-e410-4585-a2ae-0031fc8073ff@d4g2000prg.googlegroups.com...
> Hi everyone,
>
> I've upgraded our testing system to CRM 4.0 twice, and both times run
> into the same issue with apointments. When you attempt to open or
> create an appointment, an exception is thrown:
>
> "[FormatException: Metadata provided to duration control must have a
> format property of duration, found ]"
>
> I've isolated the problem to be the "actualdurationminutes" field.
> Somehow, during the upgrade, this field was changed from format
> Duration to format None. I've confirmed the "actualdurationminutes"
> field is correctly a Duration field on all the other entities
> (Activity, Task, Phone Call, etc). It is only Appointments that it
> somehow ended up broken.
>
> Since this is a system attribute, I cannot change the format nor
> recreate the field. I've been through the setup logs and the update
> on the field for Appointments is the same as for all other entities.
> There are no errors.
>
> Anyone have any ideas how to fix this bug?
>
> Thanks.