Skip to main content
Solved

Company Tree Import 2024R1 not working as expected

  • September 4, 2024
  • 3 replies
  • 69 views

martingaxiola
Varsity I
Forum|alt.badge.img

After reviewing the post where the company tree import is referred and having no luck with the examples, as the screen is changed, I tried to attempt to make it work but had no luck. 

Below is what my import looks like; also, I am using the Conctac Field as it is the only field that is allowed to be modified on the Company Tree screen. When I run the import does not give me errors, but it does not make any updates on the company tree. 


Let me know if you can see any errors on my import. I appreciate the help of the community! 

Best answer by Manikanta Dhulipudi

Hi @martingaxiola 

one quick suggestion on save action.

Please Move the save action to the last.

 

View original
Did this topic help you find an answer to your question?

3 replies

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+13

Hi @martingaxiola 

one quick suggestion on save action.

Please Move the save action to the last.

 


chameera71
Varsity I
Forum|alt.badge.img+2
  • Varsity I
  • 60 replies
  • September 4, 2024

It sounds like you're trying to import data into the Company Tree screen in Acumatica, but the import isn't producing the desired updates despite not showing any errors. There could be a few reasons for this behavior. Let's review some potential issues:

 1. Field Mapping Issues
   Correct Field Selection: Ensure that you are mapping the import data to the correct fields in Acumatica. If you're using the "Contact" field because it's the only editable field, double-check that this field is indeed the one you want to update in the Company Tree. It's possible that other fields might need to be included or correctly mapped for the update to take effect.

2. Import Scenario Configuration
   Import Mode: Make sure that the import scenario is set to update existing records rather than just inserting new ones. In the import scenario, you should configure the mode to "Update Existing Records" to modify the existing data.
   Matching Conditions: Verify that you have correctly set up the matching conditions for identifying the records to update. If the system cannot correctly identify which record to update, it might silently fail to make changes.

3. Company Tree Screen Behavior
   Screen Customization: Since the Company Tree screen has been updated, it's possible that the screen’s behavior has changed, and certain fields may no longer function as expected in an import scenario. You may need to inspect the screen's customization or version history to identify any changes that might affect the import process.

4. Testing with Manual Update
   Manual Entry: Try manually updating the "Contact" field on the Company Tree screen for one of the records to see if the system accepts changes. If it doesn’t, this might indicate an issue with permissions, validation rules, or screen customization that would also impact the import.
   Audit Trail: If possible, enable the audit trail for the Company Tree screen to see if any changes are logged when you attempt the import. This can help identify whether the import is making any changes that are not immediately visible.

 5. Log and Trace
   Trace Tool: Use Acumatica’s trace tool to monitor the import process. This can provide detailed logs about what the system is doing when the import runs and help identify where the process might be failing or skipping.

 


ed.goodman
Acumatica Employee
Forum|alt.badge.img+4
  • Acumatica Employee
  • 124 replies
  • September 4, 2024

@martingaxiola,

I do not have a sample mapping for this, but another thing you can try is to utilize the employees (EP203000) screen for this.

You can configure the mapping to add the appropriate workgroup to the workgroups tab of the employee screen, which is easier than working with the company tree screen, and will accomplish the same thing.

Hope this helps.

Ed


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings