Skip to main content

Hi, 
We created an attribute as a DateTime control type. 
This is attached as a user defined field to the PO Receipt. 

I am trying to print a report that is sorted by Item & then by the PO Receipt attribute. This is not working. 
If I sort by the PO Receipt Date, the sort does work. 

I saw an AUG forum post about using the CSAnswers table.but the data is not in that table. 
Is there a different table we should be linking to? 
Can a DateTime attribute be used to do the sorting? 
 

UDF values would be stored in the POReceiptKvExt table

@darylbowman ,
Thank you. 
Do you know how I can access that table? It does not show in the GI screen, the Report Designer or the DAC Schema browser. 
 

I’m not sure the data is made to be accessed from that table. That’s just where it’s stored.

Just for kicks, could you try something like this?

 

@darylbowman , When I do that , the field changes to DELETED when I leave the field.

To clarify, the field is an attribute attached to the PO Receipt header. 
The field show as POReceipt.AttributePort  It is defined as a DateTime Control. 
 

 

Hi @wfilipiak67 ,

Attributes are stored in CSAnswers.  Create a left join to this table from the NoteID of the POReceipt to the RefNoteID field in CSAnswers.  Also include the CSAnswers.AttributeID in the left join. 

POReceipt.NoteID = CSAnswer.RefNoteID

CSAnswers.AttributeID = ‘ReceiptDate’ (replace with the name of your attribute)

You should be able to sort on the field CSAnswers.Value

Hope this helps!

Laura

Attributes are stored in CSAnswers….

...This is attached as a user defined field to the PO Receipt...

I saw an AUG forum post about using the CSAnswers table.but the data is not in that table. 

Attributes attached as UDFs are actually not stored in CSAnswers.

This post may shed some light on the DELETED bit. I’m not positive the date conversion would even solve your issue, and I’m guessing you don’t want to group by that value.

You may be out of luck.

Thanks @darylbowman , my bad.

@darylbowman , I am thinking that the attribute is not the way to go. 
I am going to propose a custom field that we can use. 

Thank you for the assistance.

Hi @wfilipiak67 were you able to find a solution? Thank you!

@Chris Hackett , @darylbowman , @lauraj46 , We decided to go with a custom field & that worked.

Reply


Terms & ConditionsCookie settings