As per our discussion , this will also be useful in products with warranty card , where warranty card number can be entered and also in mobile phones for imei number .
Rule based UDF is not possible in the present Ginesys architecture. But there's a work-around:
Approach 1: Make these UDF fields mandatory and capture 'Not a School Student'
Approach 2:
> Create desired number of 'Editable Choice List' type UDF, and mark it as mandatory
> Set default value as 'Not a School Student'
> Now while making a POS Bill, cashier would have to go to 'Other Information' window. If the customer is buying the school product, capture related value/data in the UDF field. Else, let the default value (Not a School Student) be there.
> Using this, you can easily segregate
- Let us know if this suffice your requirement. Keep posting your Idea.
We're marking this as unlikely to implement. Though we'll review again if the idea gathers enough votes. Keep posting your idea.
Hi,
As per our discussion , this will also be useful in products with warranty card , where warranty card number can be entered and also in mobile phones for imei number .
etc
Still why have you made tis unlikely to implement
Attachments Open full size
Rule based UDF is not possible in the present Ginesys architecture. But there's a work-around:
Approach 1: Make these UDF fields mandatory and capture 'Not a School Student'
Approach 2:
> Create desired number of 'Editable Choice List' type UDF, and mark it as mandatory
> Set default value as 'Not a School Student'
> Now while making a POS Bill, cashier would have to go to 'Other Information' window. If the customer is buying the school product, capture related value/data in the UDF field. Else, let the default value (Not a School Student) be there.
> Using this, you can easily segregate
- Let us know if this suffice your requirement. Keep posting your Idea.
We're marking this as unlikely to implement. Though we'll review again if the idea gathers enough votes. Keep posting your idea.
Attachments Open full size