Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Generating code with errors for opportunity/opendeals_date #16

Open
rogerhillgsy opened this issue Jul 28, 2021 · 3 comments
Open

Generating code with errors for opportunity/opendeals_date #16

rogerhillgsy opened this issue Jul 28, 2021 · 3 comments
Labels
bug Something isn't working
Milestone

Comments

@rogerhillgsy
Copy link

rogerhillgsy commented Jul 28, 2021

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

@scottdurow
Copy link
Owner

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?

@rogerhillgsy
Copy link
Author

rogerhillgsy commented Jul 29, 2021 via email

@scottdurow scottdurow added this to the v2 milestone Jun 14, 2022
@scottdurow scottdurow added the bug Something isn't working label Jun 14, 2022
@RhINO-CRM
Copy link

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants