Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help with import of XML file into Peachtree database from VB.NET

Status
Not open for further replies.

tsfllc

Programmer
Dec 8, 2009
4
US
I applied for Silver Level Partnership with Sage for integration with Peachtree last Friday...hoping I would be able to continue design of Customer, Vendor, Sales Journal & Check Payment imports into Peachtree. My understanding is that more detailed information and access to forum(s) would be available to me.

I haven't received any correspondence from Sage yet and am in dire need of support on a couple of issues before I have a demonstration today regarding the integration I don't have finished yet.... :)

Before posting any more info, can someone help me with determining where I may have a problem with importing into Peachtree Complete 2010?

Once my prospective customer's CPA sees my integration process and signs off on it, my 10K sale would be complete.

Please help!
 
More information is needed in order to help you with importing into PCW2010.

The best thing to do is to review the help information in Peachtree for importing files.

I have had luck exporting a file from the sample company, opening the file in Excel and reviewing the data that is exported (order, special ids (like gl account type for cash is 0, while income is 21, etc.).

When importing information, Peachtree can only alert you of one error at a time.

 
I didn't even think about attempting to import using Peachtree's menu option.

I see that the default file type displayed in the form is CSV. Can I use the XML file I am generating through .NET ?? If so will Peachtree generate errors if the node names in the XML file are improper? I'm thinking that this may be part of my problem else it has to do with not including all required fields.

At any rate, I'm going to test with my file right now. I'm also including the attachment of my XML file for your review.

 
I apparently didn't do that correctly. I'm going to paste it instead.

- <PAW_PaymentsJournal xmlns:paw="urn:schemas-peachtree-com/paw8.02-datatypes" xmlns:xsi=" xmlns:xsd="- <PAW_PaymentJournal xsi:type="paw:payment">
<Vendor_ID xsi:type="paw:ID">AgTest1</Vendor_ID>
<Vendor_Name>Ag-Test Inc.</Vendor_Name>
<Date xsi:type="paw:date">12/7/2009 12:00:00 AM</Date>
<Check_Number>120003</Check_Number>
<Name>Ag-Pilots Inc.</Name>
<Line1>3986 Industrial Parkway</Line1>
<Line2 />
<City>Tipton</City>
<State>WA</State>
<Zip>59038</Zip>
<Cash_Account xsi:type="paw:ID">1020</Cash_Account>
<Cash_Amount>-594.72</Cash_Amount>
<Memo />
<Number_of_Distributions>1</Number_of_Distributions>
- <PaymentLines>
- <PaymentLine>
<GL_Account xsi:type="paw:ID">6010</GL_Account>
<Amount>-594.72</Amount>
</PaymentLine>
</PaymentLines>
</PAW_PaymentJournal>
</PAW_PaymentsJournal>
 
Using the Peachtree import is a bit tricky.

The first thing to know is that you have to import things in the right order. example you can't import a sales order before you import the customer.

Another point is that the data is validated. That means that you will get records ignored or worst if they have invalid data like a bad account number.

Peachtree does have help info about this but it often isn't clear.

Final point doing this takes a well trained power user. Otherwise you get tons of errors.
 
As of today, I've gotten customers, vendors, sales invoices and payments to import through my .NET form. I nixed the use of the Peachtree import form.

I'm waiting for Sage to approve my application. At which time hopefully more documentation will be available for the above integration.

It's frustrating when certain fields won't import and they appear to be simple and straightforward.

And, yes, needless to say, you have to put the customers/vendors in first because the sales invoices & payments refer to a customerid/vendorid that must already exist.

Are you familiar with any other documentation that exists that was not created by Sage?
 
If you can get a handle on the old DDE manual that would help. You should also check out Pawcom.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top