1 Topic by randomizer

(0 replies, posted in FA Modifications)

Hello FA team:

I need persistent purchase prices for all of my inventory items.

To prevent the auto-updating of purch_data.price when entering an invoice or grn for an item, I commented out the function calls to add_or_update_purchase_data in:

/purchasing/includes/db/grn_db.inc
/purchasing/includes/db/invoice_db.inc

Seemed to do the trick, as I can still change my purchase prices from the /inventory/manage/items.php? page.

If anyone can tell me if I've broken anything that'd be swell. I grep'd for more calls to that function but don't see it anywhere. I also don't know if purch_data.price is used for anything but prefilled info.

Insights would be very helpful. Thank you for the cool project.

Go to forum: FA Modifications

2 Reply by randomizer

(3 replies, posted in FA Modifications)

Hi Scott,

Yes. My item naming scheme was devised while using QuickBooks. There are many impacted tables in FA's database but I was careful to alter each of them before importing a portion of my item list.

I'll post again if I have a problem with it and hopefully a veteran can chime in.

Go to forum: FA Modifications

3 Topic by randomizer

(3 replies, posted in FA Modifications)

Hello,

I have modified my stock_id and item_code database columns as well as the items.php text input to accept and store 40-character item codes/stock id's rather than only 20. I left the datatypes the same; varchar or char.

Imports (with the CSV extenstion) and new items appear to work normally. I can say that a stock check sheet is kind of ugly with codes longer than 20 characters, but this is not too big of a problem.

Does anybody have experience with other parts of the application that should be modified for longer item codes/stock id's? My instinct tells me that the modification is complete, but confirmation or warnings would be very helpful. I am very new with php and mysql.

cheers

Go to forum: FA Modifications