Skip to main content
Solved

Cubic meter in grid displays different when deployed than in local environment


Forum|alt.badge.img+4

Hey all,

I am having an issue.

i concatenated a value with cubic meters but i am having an issue with displaying it in my grid.
When i look at it in my local environment it displays correct:

these are the values in my database:


But when i deploy it, it looks like this:
 

Any idea what could be causing the issue?

Best answer by Timothy Mentowidjojo

Hey @Mark Jongeling,

It looked fine in the functionality screen and generate source code process but not in the devops repo. We are using 2023.1.12.0. We settled with using m3 and ft3 instead.

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

5 replies

Forum|alt.badge.img+4

btw the values from my database are from a view and the values that are displayed in the grid are via a lookup


Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Timothy,

Is the column in the View a Nvarchar? Whilst the model may say it should be a Nvarchar, the View code on the database may return data as Varchar. Casting the column as Nvarchar will solve that. 

Hope this does the trick!

 


Forum|alt.badge.img+4

Hey @Mark Jongeling , that didn’t help.

I provided you with the view below. An extra character gets put after deployment which is weird.


Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Timothy, 

It looks to be that when generating the code of the View that the encoding is the problem. Do you use the Functionality screen or the Generate source code process? In my test in the upcoming 2023.2, I do see the correct result.


Forum|alt.badge.img+4

Hey @Mark Jongeling,

It looked fine in the functionality screen and generate source code process but not in the devops repo. We are using 2023.1.12.0. We settled with using m3 and ft3 instead.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings