Reporting module problem - obs # instead of the name

[Agnalda da Graça]

Hi guys

I´m using OpenMRS 1.9.1 and I´m having a problem with my reports. The reports that I use concepts, instead of appearing the name/value it always appear obs # (number). For example, for the diagnosis column, instead of appearing ´Diabetes´ or ´Hypertension´ it only appears obs #1056 (ex.). I was using reporting module version 0.7.3.1, I upgraded to 0.7.4.1 and then to 0.7.5 but the problem continues. I once made a dump of this database and restored in another machine with reporting module 0.7.3.1 and it was working fine. I had to do the dump again for the same machine and now the other machine has the same problem. Can anyone help? 

[James Arbaugh]

Hi Agnalda de Graça,

 

I wonder if the concepts have names for the locale that you’re using?  I would try the English locale and see if it still happens? 

 

What type of report is in the screen shot.  If it’s an SQL dataset, it could be that you’re not doing the lookup to find the name.  With SQL that has to be done manually, since the coded data is stored as the concept number.

 

I hope you have found a solution to the other problem you had last Friday.  I’ve never seen those error messages.

 

I wish I knew exactly what the problem you ran into was, and how to fix it. Hopefully those suggestions will help get you started, or someone else will be able to give their 2-cents.

 

Thanks,

James

 

From: implem...@openmrs.org [mailto:implem...@openmrs.org] On Behalf Of Agnalda da Graça
Sent: Tuesday, April 16, 2013 6:19 AM
To: implem...@openmrs.org
Subject: Reporting module problem - obs # instead of the name
Importance: Low

 

Hi guys

Im using OpenMRS 1.9.1 and Im having a problem with my reports. The reports that I use concepts, instead of appearing the name/value it always appear obs # (number). For example, for the diagnosis column, instead of appearing Diabetes or Hypertension it only appears obs #1056 (ex.). I was using reporting module version 0.7.3.1, I upgraded to 0.7.4.1 and then to 0.7.5 but the problem continues. I once made a dump of this database and restored in another machine with reporting module 0.7.3.1 and it was working fine. I had to do the dump again for the same machine and now the other machine has the same problem. Can anyone help? 

--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
 
 

[Wyclif Luyima]

Hi Agnalda,

It looks to me like you are printing the obs itself rather than the obs question concept, I'm not sure about how you are doing this but you need to reference the obs concept .

Does this make sense?

Wyclif

--
Wyclif Luyima
Regenstrief Institute Inc.

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.

[Pascal Brandt]

Agnalda, perhaps you can paste the SQL query if it's a SQL cohort query you're using?

[Michael Seaton]

Hi Agnalda,

Sorry for the delayed response, I have been away.

I am assuming that you are using a Row-per-patient dataset in your report, which is being displayed in the standard web renderer.� Based on the code I see there, any columns that contain "Obs" as values will be displayed by using the Obs.getValueAsString(Locale) method, which under normal circumstances will return the name of the Concept that is recorded as an answer.

However, if an error occurs in the code while trying to display the value in this way, the fallback behavior is to display the column value by calling toString() on the object, which seems to be what is occurring here.� Unfortunately, the code swallows the actual error that is occurring, so your logs will not likely be able to tell you much more about the reason for this error (if indeed this is what is happening).

Is it possible that the Obs that you are trying to display for either the question or the answer have incorrect datatypes associated with them?� For example, you are storing and displaying coded values, but your question is configured as a numeric or a complex datatype?

Mike

On 04/17/2013 01:19 PM, Wyclif Luyima wrote:

Hi Agnalda,

It looks to me like you are printing the obs itself rather than the obs question concept, I'm not sure about how you are doing this but you need to reference the obs concept .

Does this make sense?

Wyclif

On Wed, Apr 17, 2013 at 11:08 AM, James Arbaugh <jarb...@hashaiti.org> wrote:

Hi Agnalda de Gra�a,

�

I wonder if the concepts have names for the locale that you�re using?� I would try the English locale and see if it still happens?�

�

What type of report is in the screen shot.� If it�s an SQL dataset, it could be that you�re not doing the lookup to find the name.� With SQL that has to be done manually, since the coded data is stored as the concept number.

�

I hope you have found a solution to the other problem you had last Friday.� I�ve never seen those error messages.

�

I wish I knew exactly what the problem you ran into was, and how to fix it. Hopefully those suggestions will help get you started, or someone else will be able to give their 2-cents.

�

Thanks,

James

�

From: implem...@openmrs.org [mailto:implem...@openmrs.org] On Behalf Of Agnalda da Gra�a
Sent: Tuesday, April 16, 2013 6:19 AM
To: implem...@openmrs.org
Subject: Reporting module problem - obs # instead of the name
Importance: Low

�

Hi guys

Im using OpenMRS 1.9.1 and Im having a problem with my reports. The reports that I use concepts, instead of appearing the name/value it always appear obs # (number). For example, for the diagnosis column, instead of appearing Diabetes or Hypertension it only appears obs #1056 (ex.). I was using reporting module version 0.7.3.1, I upgraded to 0.7.4.1 and then to 0.7.5 but the problem continues. I once made a dump of this database and restored in another machine with reporting module 0.7.3.1 and it was working fine. I had to do the dump again for the same machine and now the other machine has the same problem. Can anyone help?�

--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/

�
�

--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/

�
�

--
Wyclif Luyima
Regenstrief Institute Inc.

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.

--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/

�
�

[Agnalda da Graça]

[Agnalda da Graça]

Hi

Thanks for your response. Im using a Row-per-patient dataset yes.
I was using openmrs in 1 machine (M1) that was working fine, but I had to do a backup and restore it in another machine (i will call it M2) that has this problem. So, the M2 had the data from M1, I made a backup from M2 (with the data from M1) and after that the reports come with this problem even in other machines.