Using RQM excelExporter in non-US locale
The technote mentions that the RQM excel exporter works only if the locale is english (US)..
A client from Turkey does not have a machine with US locale - does it mean that the excel exporter cannot be used in that machine? Or is there anything to be done to make it work?
A client from Turkey does not have a machine with US locale - does it mean that the excel exporter cannot be used in that machine? Or is there anything to be done to make it work?
2 answers
Hi Sunil,
I'd look at these other variables first.
Given the version for this technote is old (vs 2.0.1) and a possible cause referencing Excel 2003 which is also old, I wouldn't assume (yet) this is the cause.
Do you have a working environment with the same Excel and Import versions as the client?
And if you switch the locale to Turkey, does it stop working?
Is there no one in the organization that has a machine that can change to US Locale and test? Or who has a higher version of Excel?
You didn't say specifically what the problem is. Is the client experiencing the exact symptom: "Nothing happens, when you click in Excel RQM > Export to file". Does it work if they Export to a server?
Is there anything in the Import log? Anything in the Windows Event Viewer?
I'd look at these other variables first.
Comments
Hello Antoinette Iacobo, Thank you for the inputs.
We have evidence to believe that the issue is caused due to non-US locale..
Basically the client has validated that the RQM excel exporter works as expected if the machine locale is set to US.
But they do not want to do so because they have other applications on the machine which will be impacted by this change.
They are trying with a compatible version of excel exporter for CLM v4.0.3.
Best Regards
Sunil
RQM excel exporter utility needs the US locale in order to be able to communicate with any application. It is a limitation from MS Office solutions including Excel, Word, etc.
Here is the technical article from Microsoft which mentions this
Best Regards, Sunil
Here is the technical article from Microsoft which mentions this
Best Regards, Sunil