By using this website, you agree to our Terms of Use (click here)
Good Morning,
This seems like it should be an easy thing to import. I have installed a test acumatica server running the same version our vendor uses. 5.3. I understand that equipment is defined in one screen, projects in another. Then in a background, a pivot table forms the relationship that binds projects to equipment. Here is the issue, logically, I should only need a project id and equipment id in a import to create a new entry. The idea is one file with just two fields, the project id and the equipment id. However, I do not seem to be able to get this to function, it runs but 0 records are processed. I have attached screen shots showing my setup. Hopefully this is something that is possible. I see most examples seem to be imports that deals with one object, while this is something that deals with binding two object together. Any help here is greatly appreciated because we have folks entering a ton of data manually. I can provide access into the test server if that makes things easier as well.
Two field file ~Is it weird I think programming it would be easier? lol? No database access into production server though. I did try finding instructions, but there appear to be many missing details from what I can find.
Data Provider
Data Provider Schema
Import Scenario, tried a couple things here, this is what I ended on.
Final screen with green check but no actual import. Both ID's do exist.
I ended up getting this working. Anyone who may find it useful, image of correct import scenario below. The confusing item on this screen is that there is no distinct where clause, i.e. update where id = passedid. Also, would be nice if they completely abstracted the "real" background ID's, eh turning into a rant lol.
*Note*, the second line targets the correct project passed on the passed project id. I guess this is linked up by it being a key field and not having a commit checked.
Thanks for sharing your solution SQLRunner. Normally, the Import Scenario functions like a "macro on a screen" in that whatever you feed it acts like you are typing the value in to the screen. So, your "DREAMCAST" value should have worked. Maybe you found a bug.
Hi Tim,
No problem, I do believe I found a bug in this version related to the break on error feature. The same outcome occurs on our vendor implementation and their support team does not have an answer for it. BTW, do you know if its possible to use the import scenario to remove objects/relationships? i.e. a file that removes the equipment from the project? Our vendor implied that you can only add and not take away.
You can mass delete using a GI. If you have a way to tag your list you can quickly delete items. That's been my go-to method. Just go to the entry tab and select "enable mass deletion".
You should also be able to use an Import Scenario if you are "importing" into a screen that has a Delete action like the Bills and Adjustments (AP301000) screen:
