Attibutes are not displaying the value, instead the attribute ID in CSanswers table

Hi ​@rodrigocid34,

You need to join CSAnswers to CSAttribute on AttributeID = AttributeID, then join CSAttribute to CSAttributeDetail also on AttributeID = AttributeID and display the descr field from CSAttributeDetail table.

This link will helps you to display the attribute values in report.

Hi Dipak,

but why is not working using the virtual field in the stock ítem Stockitem.Categoria2_attributes? The curios thing is that the same report, in a test tenant with a backup data from production is showing the value that I need which is stockitem.categoria2_attributes 😐

Is it possible the report was changed since the backup?

No, report is the same in Test and Production. And is not only the report, is the GI too. GI in Test shows the value of the attribute in the item and the same GI in Production shows the ID of the atttibute.

Is the test tenant part of the same Acumatica instance as production?

Correct!

Sometimes odd behavior can be resolved by restarting. I’m afraid I can’t offer much else.

I did it, also restarted cache and nothing. Thank you any way Daryl! 💪

I just wanted to add onto this thread I’ve had two different clients suddenly have issues where the projected attributes suddenly change from showing the descriptions to showing the values. I’m aware you can map in more attribute tables to fix it when it happens. My question is, why does this suddenly change? It is convenient to have those attributes easily available to add to common GI’s and reports. But when they prove unreliable, customers get frustrated with us. Has there been any explanation as to why the change can happen at random times, without an apparent cause?

Hi ​@philr75, 

Are you sure that attributes configuration are not being changed by some user in the INTERNAL checkbox? Because I thought at first the same thing that you but in reality, a user “turned off” the internal field.

Edit: I didn’t notice but my other user ID was logged in just now (this is philr75 logged in by mistake to uarkassist60). I can’t rule out that possibility of user changing the field but at the same time, its such an obscure field that I can’t see it happening. I could go turn on audits and watch for it but the other client saw it happen right after an upgrade. I didn’t know about this field at that time so I didn’t think to go check it. I’m curious to see what support has to say. They were quick to tell me to map CS tables to the GI in that older situation but there wasn’t an explanation as to why for years the correct information would display and then suddenly switch from showing the description to showing the value ID.

I had a similar issue and I was using Attribute Value but I should have been using Attribute Caption