Page 1 of 1
LANSA Documentation gives odd results
Posted: Fri Nov 12, 2021 10:28 am
by LANSAfolks
I was wondering if anyone else have has experienced issues with the LANSA documentation website search? I searched for SET_SESSION_VALUE today and got a single result back with a page in Japanese. Next I searched for AsString and got irrelevant results? I am beginning to miss the old .chm files.
Re: LANSA Documentation gives odd results
Posted: Fri Nov 12, 2021 2:40 pm
by BrendanB
If you do get Japanese results, check the URL:
https://docs.lansa.com/14/ja/lansa015/c ... _value.htm
you can change the parameter that has 'ja' to 'en' and it should give you English results.
Re: LANSA Documentation gives odd results
Posted: Tue Nov 16, 2021 1:31 am
by Dino
if you change the ja to en, you can also change the 14 to 15:
https://docs.lansa.com/15/en/lansa015/c ... _value.htm
Re: LANSA Documentation gives odd results
Posted: Tue Nov 16, 2021 6:02 am
by atostaine
Anytime I click F1 in the IDE I get file or directory not found. I have to change it to V14 in the URL. Anyone else seeing that?
Re: LANSA Documentation gives odd results
Posted: Tue Nov 16, 2021 7:00 am
by Dino
what version of VL and in what screen are you when it happens? I dont see that problem in V15.
better to report it to support.
Re: LANSA Documentation gives odd results
Posted: Tue Nov 16, 2021 11:39 pm
by adale
Art,
I was seeing the same issue with page not found. When I spoke to support (a while back) they acknowledged that the documentation site(s) was being updated and most the links were broken at that time. They stated it is being worked on, and with epc 150040, I have seen more F1 prompts bringing up a support page, but quite a few seem to just be generic or high level topic and not specific (such as:
https://docs.lansa.com/15/en/lansa015/c ... invoke.htm).
I am hopeful with new epc releases, this will improve.
Re: LANSA Documentation gives odd results
Posted: Wed Nov 17, 2021 1:22 am
by atostaine
Weird it requires an EPC. Simply changing 15 to 14 in the url works. Unless it’s a new v15 function