I am using this procedure to import Vendors into the VendTable table. It works fine, but sometimes, I need to delete all the vendors I've just created and tweak the data and then would like to try again.
But it seems once an Definition Group has been used to import data, it can't import any more again.
I get: "No data imported" in the InfoLog.
The only way I can do this is by recreating a new Definition Group via the Template Wizard which, well, I don't want to.
Any ideas to be able to reuse a Definition Group?
Thanks.
I was able to reset the Definition Group status doing: Select the Definition Group, click Table Setup button to the right, in the Import Status column, select Import. Save. Run the import again.
Related
currently I'm trying to import approx 1600 tasks from Azure DevOps Kanban board to another one (via browser). I've faced two problems by doing this:
It is not possible to import the task with Closed Date field, it says:
Value of a readonly field Closed Date was modified. Please revert the Closed Date values or remove the column from the input file and and try to import again.
Removing the column with "Closed Date" will cause issue with default state "Done", it says:
The field 'State' contains the value 'Done' that is not in the list of supported values.
I've copied (manually) the project settings from old Organization to new, such as:
Process \ State (and assigned it to the project):
Time and Locale as it was set in old Kanban
Also, I had to remove the ID column, because it caused the issue:
Still it is not possible to import all these tasks because of the issues. I'm looking for any tips how to fix this.
Below there's an example of CSV:
Work Item Type,Title,Created By,Created Date,Assigned To,State
Issue,Some test task number 1,TestCreator,02.06.2020 15:19:24,TestWorker,"Done"
Issue,Some test task number 2,TestCreator,02.06.2020 15:20:23,TestWorker,"Done"
When importing work items via CSV file in Azure DevOps, first make the following statements are true:
1.The source project to export and target project to import has the same work item type configuration, in common, they need to have the same process configuration, for example, work item type, state.
2.All work items you import are created in a new state. This rule means that you can't specify field values that don't meet the field rules for the new state. (That's why "Done" that is not listed as supported value)
3.Make sure you don't assign IDs to new work items that you're adding. Work item ID is unique in one Azure DevOps organization. (ID will cause the following error message)
With the above prerequisites, the import process loads the imported work items into the queries view in an unsaved state. No IDs are assigned. Verify the results are what you want. Then, choose Save Items to save the work items.
If you still get the error when importing, try reduce the work item counts for per import attempt. As you said, you have approx 1600 tasks, you could import by separating them into several queries.
i'm trying to import res.partner data with csv import.
I did an import compatible export of the child_ids/* fields as i'm trying to generate shipping adresses.
I already managed the corresponding main contacts, but every shipping adress is created twice, no matter what i try.
i tried the following formats
please see the image https://ibb.co/d2kw7fY
No matter how i format it, the contacts are correctly created under the main contact, but i have each delivery contact created twice.
Could anybody give me an insight how to get it ?
Thanks
I created an data source 'CSV' that has 2 columns. receipt_to and inventory_id.
I want to change the on the warehouse details screen, the default receiving location to Main, from whatever it currently is.
I created an import scenario and tried to configure it multiple ways. I can't get it to work. Sometimes I receive an error that either the value "Main" or the field "Default Receipt To" doesnt exist. I don't understand the error because I am sure both the field (which I selected) and the value "Main" is a legitimate location
See image
Kyle, add "Warehouse" also in your input file. So, your input file must have InventoryID and Warehouse. and your import scenario must be like this.
I am trying to start the T100 courses for Acumatica and the instructions mention to setup a development environment and then start working on some examples. The first example has you create a graph for the Country table using the PXGraph template, build the RB project so you can use the created graph in the site project, create a ListView page pointing to the graph you just created, and then use the Data Access Class Generator to create the Country class for you in the DAC folder.
Which would be great, however when I click on 'Generate Class' for the data source it brings up the DAC Generator window . . . with no tables listed. So I'm supposed to select Country but nothing is there to select. I have no idea what I'm doing wrong, so if anyone has any thoughts on how this list is populated that would be great. Thanks.
Data Access Class Generator with no tables image
On the same place where you are trying to click Generate Class, you have to right click the page and click Refresh.
There is no shortcut, too.
I spent 2 hours ambling around after overlooking that step during tutorial.
I'm not sure what was wrong, but I closed my solution and re-opened and the next time I tried the tables were listed. Magic.
I'm starting a new project and want to do my requirement management with Enterprise Architect.
It look really nice to define requirements, associate use cases, design elements, test and so on, all in one software.
I succeeded in creating a profile that let met drag custom requirement with predefined tagged value for enterprise stuff.
My problem is that the requirements must be manage at 3 level. The team, the management and the client. The management and the client both communicate with Excel.
My question is, it is possible to do something like:
- Create requirements diagram in EA with predefined tag value
- Export requirements in Excel (with predefined tag value) - I haven't been able to export my predefined tagged value.
- Modify the excel file
- Import from excel and update the requirements in EA.
Yes, you can do this using CSV Import/Export.
The ability to include tagged values in CSV import/export was added fairly recently, so make sure you're running an up-to-date EA (at the time of writing, the latest release is 9.3.931).
Assuming you've got all the requirements in a single package, proceed as follows:
Right-click the package in the project browser, select Import / Export -> CSV Import / Export.
Click the Edit / New button in the upper right corner of the dialog that opens.
From the Available Fields list, select GUID, Type, Name, Notes and any other fields you use (eg Difficulty).
Click Add Tagged Value Field -> Value.
If the tag you're after is defined in a properly deployed UML profile, you can find it in the list. Otherwise, click the Other Element button and navigate to one of your requirements; this will allow you to select tags created on-the-fly as well.
Back in the Specification dialog, make sure you've selected the correct delimiter (upper right corner) and set a name for the specification. The other dialog options can be left empty but it's probably a good idea to specify Requirement as the default type. Save the specification and close the dialog (you only have to create the specification once, of course).
In the Import/Export dialog, specify a filename and select Export. Click Run to export the requirements.
To reimport, simply select to Import rather than Export in the CSV Import / Export dialog.
The two crucial fields are the GUID and the Type. You may want to hide these columns when you send the requirements to management and client, and inform them that they shouldn't tamper with those.
The GUID is the unique identifier. As long as that's in the file, EA can reimport the file and update your modelled requirements.
The Type needs to be set to Requirement for any new requirements that are added in the file. You don't need to set a GUID. EA will ask you during the import whether to create one or ignore the entry completely; tell it to create one and the requirement will be added to your model. But the Type field has to be set or EA won't know what to create.
What EA won't do is delete requirements from your model if they've been removed from the file. This is something you'll have to manage manually. (And if you're working on a project where the number of requirements actually decreases over time, please give me a call.)
If your requirements are in several packages you can still import / export them this way, but it's a little bit more complex: you'll need to set the Preserve Hierarchy option in the CSV specification and use a couple of special columns, but that's pretty well described in the help file.