I use the framework to create an Overdue Charge. In previous 5.20 version, there is no issue. I upgraded the site to 6.0. Now an error occurs:
Error #115: An error occurred during processing of the field IsRUTROTDeductible : Index was outside the bounds of the array..
I create the ARInvoiceEntry graph. Next the ARInvoice DAC, and populate the header fields. Finally I call graph.Document.Insert(overduecharge). Transactions are inserted later.
I do have some user fields in an extension table 'ARRegisterExtension'. But that table uses the default InnerJoin, with the matching records from ARRegister included in the table
Please advise if an extra step must happen with RUTROTDeductible. I'm not familiar with this entity.
Try to search for RUTROT in your code.
These fields were moved to an extension in 6.0, so these fields will not be available in ARInvoice DAC any more.
If you are setting these fields anywhere, please remove this code.
These fields are for Sweden users only, so, I don't think you need to set it.
Related
I'm working with a client on obtaining Bills and Adjustments values through the Contract based web services. I understand that certain fields aren't available in the Default Endpoint, and have to be obtained through an extension.
I'm trying to add fields from the Bills and Adjustments' Applications tab, but I'm running into a warning that I don't understand. If I extend the Default endpoint for 'Bills' (call it 'BillExt'), and I try to add the Reference Number field from the 'Applications' tab/grid (or any other field from that grid) - I get the following warning (see screenshot below)...
Can someone explain what the issue is, and how I go about adding these fields from the 'Applictaions' tab/grid? I've added fields from the 'Approval Details' grid without this warning without a problem. Is this a warning I can disregard?
You are trying to add a field from another table/view that can return multiple rows for a single Bill.
The correct way to do this is by adding a separate collection on the object and map the view on that collection. e.g: Applications or Details collections here.
That collection will have the information for all records related to the header once you retrieve them using the ?$expand=Details on the query string request.
We have Manufacturing package version "MFG - 19.102.0051.25 - 2019.05.06" published in our instance. Along with this we have our own customization package. We recently developed a process screen which brings in data from ARRegister and ARTran tables. We also have some custom fields created in ARTran table, on process button action we are doing some calculations and storing values in custom fields of ARTran table.
We are not using any Manufacturing related fields in this process screen. The issue is when do process the records we are getting error saying Invalid column names from JAMS tables. What might cause this issue? See the attached screenshot:
https://i.imgur.com/Q27uhNf.png
I have dirty hack for you to use.
I'd suggest you to create columns, for lack of which code complains and execute your process again.
Overall it could be that some package has dependency from that fields, or may have in the future.
I am trying to create a Journal Transaction of AR module from Shipment screen with new button, on this new button click, it should create Journal Transactions document with credit amount in one account and debit amount in one account, These two accounts are configured in shipment screen only. but am getting below error. I am passing Project and all the other mandatory field values from code.
Error: Inserting 'GL Transaction' record raised at least one error.
Please review the errors. Project is Required but was not specified. Account '40000' used in the GL Transaction is mapped to Project Account Group.
You need to either pass in the project from the shipment (if the journal transaction should hit the project) or pass in the default non project value.
for example if not setting the project from the shipment you can set your project field on the journal lines using the following:
myInTran.ProjectID = ProjectDefaultAttribute.NonProject();
If you are pulling the project from the shipment you need to set the journal tran lines for the ProjectID, TaskID, & CostCodeID fields.
Depending on the version of Acumatica you are using, you might not have CostCodeID. I think it was added in 2018R1.
If using the Non project value, the TaskID and CostCodeID are not required.
I am having the following inconvenient when inserting a
custom field on a DAC extension, with Acumatica 17.202.0016 and
18.103.0022 version. In both versions I followed the next steps:
1) Created a "Usr" field "UsrCustomString", on the Opportunities page
CR304000, followed by creating its controls and publishing
the customization project.
Creation of "UsrCustomString" field
2) Then I selected an existing Opportunity and assigned a value in the new field.
Updating record with new value
Checking in DB the updated value
After doing this, I noticed that after navigating
to the next record and then selecting back the
OpportunityID "OP000368", the custom field shows blank. The same happens after pressing the cancel button.
Field is shown blank
I tried this sequence in the Cases page "CR306000" and it worked
correctly. It seems an issue related to the CROpportunity DAC.
Definition of the DAC extension with "CustomString" value
The solution that #cbetabeta, worked well for me. Here is the link for the solution
Custom field on CROpportunity doesn't display saved value since upgrading from 6.10 or 2017R2 to 2018R1
I have some javascript code attached to the accounts entity. This code sets the requirement level of the primary contact attribute based on the value of a custom option set field showing various account types. This was developed on one server, where it worked, and so the solution was imported into another organisation where it now doesnt work.
It seems to be only on this field as i have changed the code to look at another field and that works fine. The error it gives is that the "Object doesn't support this property or method". Also what is strange is that the field doesn't appear in the list under the entity within the solution despite it being a system field.
The code i'm using is:
Xrm.Page.getAttribute("primarycontactid").setRequiredLevel("required");
Can anyone help me figure out what it's doing?
Thanks
EDIT: Found that the code is actually making the field required despite the error, but it's not displaying the * next to it. Also if I make the field required in it's settings then it does the same thing