You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running dataverse-gen to generate early bindings for my opportunity, I am seeing the following code generated for
the opendeals_date attribute. This is a built in attribute on opportunity.
// Open Deals(Last Updated Time) DateTimeType The date time for Open Deals. DateAndTime:UserLocal opendeals_date?: Date | null;
Also this a few lines below: - // Open Revenue(Last Updated Time) DateTimeType The date time for Open Revenue. DateAndTime:UserLocal openrevenue_date?: Date | null;
There are 18 DateTime fields in my opportunity, and only 2 show this problem.
The only thing that stands out to me is the fact that in the two failed cases the display name ends in a ")"
Some obscure bug with regexes causing a spurious carriage return, perhaps?
Using CRM online Database version 9.2.21071.00134. 2021 Release Wave 1.
Dataversify version 1.0.10
The text was updated successfully, but these errors were encountered:
Thanks @rogerhillgsy - there is an open bug where display names that contain new-lines cause this issue - could you check if the display name contains a CR/LF?
I believe this also happens with descriptions withe line breaks, which I think might be more common than line breaks in the display name. But I might be mistaken.
When running dataverse-gen to generate early bindings for my opportunity, I am seeing the following code generated for
the opendeals_date attribute. This is a built in attribute on opportunity.
// Open Deals(Last Updated Time)
DateTimeType The date time for Open Deals. DateAndTime:UserLocal
opendeals_date?: Date | null;
Also this a few lines below: -
// Open Revenue(Last Updated Time)
DateTimeType The date time for Open Revenue. DateAndTime:UserLocal
openrevenue_date?: Date | null;
There are 18 DateTime fields in my opportunity, and only 2 show this problem.
The only thing that stands out to me is the fact that in the two failed cases the display name ends in a ")"
Some obscure bug with regexes causing a spurious carriage return, perhaps?
Using CRM online Database version 9.2.21071.00134. 2021 Release Wave 1.
Dataversify version 1.0.10
The text was updated successfully, but these errors were encountered: