Please can anyone answer.
I have a problem during creating Invoice from Appointment which has Bill to Customer different from Customer of the Appointment.
Error: An error occurred during processing of the field Account value 2869 Error: 'TaskID' cannot be found in the system.
And I have no idea what can course this issue
Related
I try to import customer refund scenario but it got error as "Document is out of balance" like the below picture:
Do you have some applications imported along with Customer Refund?
In Acumatica you are not allowed to create Customer Refund that is not fully applied to some document.
So, if you are trying to create Customer refund without any applications(or if sum of application amounts is not equal to refund amount), you'll get this error.
So, either create document along with applications or create document On Hold(that is Hold checkbox selected).
Document having On Hold status considered as draft and can be saved unbalanced.
I keep getting this error when executing a transaction on rate object id's that were created a few days ago.
{
"source": "USPS",
"code": "",
"text": "The selected shipment date must be within 7 days of 02/15/2017, 07:11PM CST."
}
Im integrating shippo with my Node.js web application. I am using shippo node.js library.
shippo.shipment.create({, function(err, shipment) {});
I built a basic store. When user gets to checkout section, I get rates from shippo. I display those rates to the user. The user chooses which rate he wants. I save the rate object id to a database.
shippo.transaction.create({, function(err, transaction) {});
I fulfill the order and print the shipping label. The application goes to the database and retrieves rate object id to execute the transaction with shippo. In return Im suppose to get a tracking # and label information, but instead I get the error.
I first thought that the rate object id only last 7 days and then expires on its own or something. When I checked the rate object id:
https://api.goshippo.com/rates/2a0b50cbc5184362a0ea2385b490bc7b
It shows object was created 2/18. Today is the 2/21. So that cant be. The error says "The selected shipment date must be within 7 days of 02/15/2017, 07:11PM CST."
What does it mean? Why did I get it?
It seems to only happen to rate object id's that were create 2+ days ago. If the rate object id was created yesterday, I could still execute the transaction no problem.
screenshot
It looks like you are using a rate from the past (not the same day) that is causing this error to occur.
When you make a shipment at the /shipments/ endpoint, you are able to specify the submission_date when creating the shipment. If you do not specify the submission_date (you would generally only do this if you know the day you plan on shipping the item out), Shippo automatically sets the submission_date to the date the request is being made.
The reason that you are getting an error, is that you're using a rate for a shipment that has a submission_date in the past. Some carriers will only permit a submission date that is the current date, or some date in the future.
You can find more details here on the shipment object that might help.
I have an payment activity report results from cardinal commerce.
In the In the above report I found Action "None Available".
I am new to cardinal commerce payment. Can any one help me why the action "None Available" is showing for the transaction?
How can I figure out what happening for the transaction with action "None Available"?
I am updating timesheet record through client script but on Submitting the record getting an error as "Invalid Subsidiary Combination".
PS: I am working on 15.2 latest version of Netsuite
I had a similar issue with one of our cost rollup script that works with time tracking(timebill) - check the accounts related the employee/project/labor item etc - if the accounts are not exposed to the subsidiaries in question - this can happen.Also if you are using consolidation or elimination subsidiary, make sure that those are not the subsidiaries in context. In our case one project was mistakenly assigned to our consolidation subsidiary thus causing subsidiary mis-match.
That error message usually means the subsidiary and employee location don't match. i.e. the employee and/or their location are not part of the subsidiary you specified.
We are seeing failure to Netsuite while updating payments via the netsuite API,
the error message we see is as below Unable to find a matching line for sublist apply with key: [doc,line] and value: [123344,null] where 123344 is the external id of the bill.
Any ideas what might be the cause of this?
Note that SuiteTalk will give you this cryptic little message when you try to create a payment for an invoice that already has an Invoice:Paid In Full transaction status.
Don't get me wrong—it's good that NetSuite has this sanity check. I just wish the error was more helpful.
"Unable to find a matching line for sublist apply with key: [doc,line] and value: [123344,null]"
There is your problem, you can't match a line if you are not passing the line number.
We had the same problem inserting new payments, but it worked using the Internal ID for the Invoice column.
Note that the mapping specification is not clear on how to identify the Invoice when adding/updating payments for it. The API requires an invoice, and it works when you provide the Internal ID for the invoice.
I get this error when creating a customer payment. Below is my code. Make sure invoiceId is invoice's internal id and amount is less than or equal to invoice amount.
CustomerPaymentApply paymentApply = new CustomerPaymentApply();
paymentApply.setAmount(amount);
paymentApply.setApply(true);
paymentApply.setDoc(Long.valueOf(invoiceId));
We were getting this error with the Chargebee-Netsuite integration. The solution was to open the corresponding Accounting Period in Netsuite and rerun the sync.
The first number [123344,null] is the Netsuite internal ID of the affected document. If you navigate to the document in Netsuite and it has a padlock this could be the reason:
Open the Accounting Period for the affected document and rerun the sync. Setup/accounting/manage accounting periods: