• rafat
  • Senior Member
  • Offline
  • From: UAE, Dubai
  • Registered: 11/28/2017
  • Posts: 550

Topic: Supplier Allocation Inquiry - Due Date

Hi,

In the Supplier Allocation Inquiry the Due Date is always in the format YYYY-MM-DD no matter  what the user preferences are, unlike the Customer Allocation Inquiry which follow the user preference's choice.

Is there a reason for that?

https://imgur.com/HNTJfhO

Post's attachments

SuppAlloc_DateFormat.png 74.5 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

rafat's Website

2 Reply by poncho1234 (edited by poncho1234 06/03/2019 06:48:09 pm)

  • From: Colombia
  • Registered: 12/29/2014
  • Posts: 629

Re: Supplier Allocation Inquiry - Due Date

@rafat; looks like a bug:-

Looking at:-

File: \sales\inquiry\customer_allocation_inquiry.php
151:     _("Due Date") => array('type'=>'date', 'fun'=>'due_date'),

and comparing with:-

File: \purchasing\inquiry\supplier_allocation_inquiry.php
142:     _("Due Date") => array('fun'=>'due_date'),

The supplier due date is not given the type 'date': or any other type.

So in \includes\ui\db_pager_view.inc

its assigned as a normal labelcell:-

File: \includes\ui\db_pager_view.inc
144:               else
145:                     label_cell($cell);

instead of a date labelcell:-

File:\includes\ui\db_pager_view.inc
114:             case 'date':
115:                 label_cell(sql2date($cell), "align='center' nowrap"); break;

I've added to mantis id #0004897

The FrontAccounting Wiki(Manual, examples, tips, setup info, links to accounting sites, etc) https://frontaccounting.com/fawiki/

3 Reply by rafat (edited by rafat 06/03/2019 06:10:48 pm)

  • rafat
  • Senior Member
  • Offline
  • From: UAE, Dubai
  • Registered: 11/28/2017
  • Posts: 550

Re: Supplier Allocation Inquiry - Due Date

Well spotted @poncho1234

rafat's Website

  • joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,107

Re: Supplier Allocation Inquiry - Due Date

This has been fixed and committed to stable repo.

Thanks @poncho1234.

/Joe