Hi All,
We have been testing the usage of BO in a multi-lingual environment. Where we are up to is:
- We have created 1 master universe and called it ‘source’. 2. We have imported, renamed, exported that as ‘target’. 3. We have a mapping table that maps the class and object names from source language to target language.
- We have written the SQL that goes in and changes the fields in the BO repository for class names + Help text and object names + helptext from source to target languages.
- We have mapped two fields from source to target changing their names as well as changing the class name.
- We have created a simple report on top of source (just the 2 fields we editted using sql).
- We have copied the successfully produced report and gone into data->view data->definition->field universe and changed it from ‘source’ to ‘target’.
When we do that BO issues a message.
‘Some of the objects from the target universe are missing or ambiguous. You cannot run the query with this universe DA00100.’
When I actually open up the testreport_source.rep file with an editor you can actually see the universe_number.object_number + textual_name of the two columns we are trying to rename. So it looks like BO is actually storing the text of the class and object name inside the .rep file. We are on BO 5.0. It makes sense that it does this because you can open a report without being connected to a universe. (We had heard that this was no longer the case.)
Question. Does anyone out there have any suggestions as to how we might change the universe the report is attached to from ‘source’ to ‘target’ and be able to pick up the new object names and class names? We don’t believe editing the .rep files is a feasible solution.
(I am guessing that if we pick up the new object/class names we will pick up the help text.)
Thanks
Peter Nolan
Listserv Archives (BOB member since 2002-06-25)
All,
Further to my previous question. I have been doing more testing and I find…
- I create two duplicate universes.
- I create two duplicate reports one pointing at ‘source’ and one pointing at ‘target’.
- THEN I run the translation process to convert the language of the target universe.
- When the report pointing at target is run for the first time it inherits the new class/object names and help text.
So, it seems BO performs a check when repointing a report from one universe to another to determine if the fields are there at the field name level not at object id level. (Actually makes sense.)
When we are live this would cause a problem with moving new reports into the different language universes.
Anyone got any ideas how to stop this test happening? Or any better ideas on repointing reports between universes. (I’ve already thought of the idea of a ‘staging universe’ for each language and that has possibilities. I’ve already tried going into the repository and changing report source name from ‘source’ to ‘target’ but it didn’t work.)
Thanks
Peter Nolan
Listserv Archives (BOB member since 2002-06-25)
You said…
So, it seems BO performs a check when repointing a report from one universe to another to determine if the fields are there at the field name level not at object id level. (Actually makes sense.)
Me…
You’re right. Since object ids would be different in different universes, BO uses object and class names to map report objects from one universe to another.
Maybe I’m missing something major but…
What if you rename ‘source’ to ‘target’, repoint the report from ‘source’ to ‘target’ THEN run the thingy that changes your object names. Export the universe and the report won’t need the old names to map to. That’s already done. It will have the ‘target’ id and new object name…
Cindy Clayton
Ask WHY until you understand!
Overlooked blessings…
Laughing so hard your sides hurt and you can’t catch your breath… Daydreams…
The feel of a child in your arms…
Listserv Archives (BOB member since 2002-06-25)
Peter
My only suggestion would be to modify the sequence of events. Try:
1.Create base universe
2.Create target universe via “Save-As” to get new universe id 3.Create report against Base universe
4.Create copy of report by changing the universe to the target
universe. With all objects still having the “base” language names you should not have to perform manual mapping. 5.Now translate target universe to new language. 6.When you open the “target” report (post-step 4) it should map
all change all names to the transalated names.
Mike McErlain
Listserv Archives (BOB member since 2002-06-25)
Because of all the problems in Europe with multi-lingual and having to maintain an application
from content and interface perspective in multiple languages, we have created for one of our clients
a server that sits on top of WebI (works on Unix and NT) and that translates in real-time the html between
the client and the server. One set of reports, one set of universes and one interface to maintain…
http://www.translation-server.com
An alternative for the above is to use @prompt to retrieve the language - this is defined in the object defined that retrieves the value from a translation table.
This does not translate the interface though.
Regards,
Maarten
Listserv Archives (BOB member since 2002-06-25)