Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Error while creating a decimal field in the January update #75

Closed
TinaMenezes opened this issue Jan 17, 2017 · 10 comments
Closed

Error while creating a decimal field in the January update #75

TinaMenezes opened this issue Jan 17, 2017 · 10 comments
Assignees
Labels
bug Product bug shipped

Comments

@TinaMenezes
Copy link

Hi,
I had created a decimal field previously in Visual studio code.
field(70000011;"Percentage";Decimal)
{
}
It worked properly previously. But now when I am creating a simple decimal field in the January update and installing the extension, my web client stops working due to the decimal field created and gives error that 'Server error has occured and the content cannot be displayed'.

image

error 2- while creating decimal field

Kindly give a solution to this.

@StanislawStempin
Copy link

Could you please try with a different field Id? It could be an Id conflict that is not handled gracefully.
We haven't noticed any issues with Decimal fields in particular.

@pmohanakrishna
Copy link

I created a decimal field and seems to be working fine.
could be something else. please add details from event viewer.
decimal

@TinaMenezes
Copy link
Author

Hi all,
@StanislawStempin I created another decimal field with different ID which is unique. It is not conflicting. I checked that. But I still get the same error while opening the web client.
field(70000005;"Average Field";Decimal)
{ }

@pmohanakrishna
I checked the event viewer. Below are the details:
Type: System.IndexOutOfRangeException
Message:
Message: Index was outside the bounds of the array.
Logical Control: Name=1001603; Caption=Average Field
Format Column Binder: 27_Item.Control1001603_Format

Kindly suggest.

@esbenk
Copy link
Contributor

esbenk commented Jan 17, 2017

We are investigating this. Seems like there is a problem with Decimals in some situations.

@TinaMenezes
Copy link
Author

Hi @esbenk ,
Ok. Thank you.

@StanislawStempin StanislawStempin added ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release and removed in-progress labels Jan 18, 2017
@StanislawStempin
Copy link

We have fixed this bug and uploaded a new azure gallery image to http://aka.ms/navdeveloperpreview. Please give it a try.

@StanislawStempin StanislawStempin added shipped and removed ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release labels Jan 23, 2017
@TinaMenezes
Copy link
Author

Hi,
Does this mean that a new VM has to be created for it again ?

@pmohanakrishna
Copy link

yes, keep backup of your .al files.

@TinaMenezes
Copy link
Author

Ok. Thanks.

@TinaMenezes
Copy link
Author

Hi @StanislawStempin,
Its working now. Thank you.

@microsoft microsoft locked and limited conversation to collaborators Apr 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Product bug shipped
Projects
None yet
Development

No branches or pull requests

4 participants