[OutSystems Maps] Japanese address string at Location parameter
Forge component by OutSystems R&D
Application Type
Reactive
Service Studio Version
11.10.18 (Build 41175)

Hello, 

When specifying Location parameter of Map block of OutSystems Maps by Japanese address string, displayed map never point the address correctly.

On the other hand, Google Maps Library's Address property can treat Japanese address string correctly.
https://www.outsystems.com/forge/component-overview/1396/google-maps-library

I hope authors solve the issue.

Sincerely,
Moriya Takasi

Hello @Takasi Moriya,


The solution for this bug has been released (today) in version 1.4.0.


Thank you for your patience.

Best regards,

Tiago Pereira

Hello Tiago, 

Thank you for announcing.

2.4.0? This is probably typo from 1.4.0:)
I confirmed the trouble has been solved.

I appreciate your team having work for the problem.
Thanks again.

Sincerely,
Moriya Takasi

mvp_badge
MVP

I edited Tiago's answer so it now says 1.4.0, in case somebody else reads the post as well :).

EDIT: and marked his answer as solution, and unmarked the previous answer marked as solution, as Tiago's post should be the final solution :).

mvp_badge
MVP

Hi,

I poked Outsystems as a bonus, because I agree that is should be solved :)


mvp_badge
MVP

Hi Takasi,

Since this is an OS-supported component, please also create a support case for this.

Hello J. and Kilian, 

Thanks for your quick responses.
Now I created a ticket for this.
When I will receive OS's response, I will share.

OutSystems Support recognized that the behavior of OutSystems Maps 1.0.0 has problems.

He wrote: 

It is in our best consideration to believe that this is misbehavior on the supported OutSystems Maps component. As such, we have created the Problem Record RPM-1015 so that a fix for this behavior can be implemented on the next release of the OutSystems Maps component. 

We would like to request your understanding given that we are unable to provide a definite fixed date for this since it will depend on the schedule of our development team.
mvp_badge
MVP

Ah, great, it's going to be fixed. Thanks for reporting back Takasi!

Hello @Takasi Moriya,


The solution for this bug has been released (today) in version 1.4.0.


Thank you for your patience.

Best regards,

Tiago Pereira

Hello Tiago, 

Thank you for announcing.

2.4.0? This is probably typo from 1.4.0:)
I confirmed the trouble has been solved.

I appreciate your team having work for the problem.
Thanks again.

Sincerely,
Moriya Takasi

mvp_badge
MVP

I edited Tiago's answer so it now says 1.4.0, in case somebody else reads the post as well :).

EDIT: and marked his answer as solution, and unmarked the previous answer marked as solution, as Tiago's post should be the final solution :).

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.