I am trying to export a large set of pushpins together with their lat/lon data out of microsoft MapPoint. The normal export to excel doesn't include lat/lon info so I tried to circumvent this problem by doing a gpx export.
Sadly the name of the pushpins seems to be 'random' (using housenumbers), hence the usability of the generated gpx file is zero.
Is there a way to define the name of a pushpin based on a field upon importing a dataset?
Hepl is much apreciated.
Not sure what you mean with that last sentence, but the Name of each pushpin can be set with the Data import Wizard using the Name and Name2 import fields.
As for your larger problem, you are on a programming site, so I assume this is an option. You could write your own exporter. The longitude and latitude information are available through the Pushpin's Location field (properties: Longitude, Latitude).
Alternatively, Support PC sell Pushpin Tool which can export pushpin information to Excel complete with longitude,latitude info.
Related
While there are multiple solutions available online to export plan to an excel, some of the export options are still in uncharted area. For e.g. i have edited few of the existing Labels to a customized name and not every label is assigned to every task under a plan. Is there any way i can export the assigned labels taskwise ?
I tried to find options in power automate but in vain. Let me know your thoughts . Thanks !
For e.g.
Here you can see task xyz has multiple Labels like Dev, Testing and Sample. If i would like to export them too into an excel sheet along with other details of the task, what would be the best way ?
Names of the labels are in the Plan Details entity, CategoryDescriptions property. You can read this once per plan to get all the names, then appliedCategories field on each task will indicate which labels are applied to the specific task. You can use the name of the property in the appliedCategories field to directly look up the value in the name from the plan.
You could also export a plan to excel from Planner directly, without writing code (which includes labels as well), in case you don't need an automated solution.
The tags do exist in each planned task but you're going to hate this, they come through in the appliedCategories object and they're represented by the order of the category itself.
"appliedCategories": {
"category2": true,
"category3": true,
"category4": true,
"category11": true
}
You can rename them all you like but those names aren't pulled through in the response.
You'll need to manage the names in your own mapping table or the like to get what you want.
To see it working, select labels in random positions and then run the List my tasks action and you'll see them there.
I am currently having a requirement where I need to extract values from a CSV file onto a template within Kofax TotalAgility designer and generate a PDF from it accordingly.
The process would pick CSV files from shared folder on the network as an input and fill a template which is in word format with merge fields with corresponding values and generate a PDF from the populated word document as an output to another shared folder.
Any help is much appreciated.
Reading CSV
There is not anything built into KTA that will handle the CSV file. I would recommend you handle this in C# (preferably your own dll rather than a script activity). The specifics of how you store the CSV data you read will probably depend a lot on how exactly your template is organized and the specifics around your data. But ultimately you will want data in separate KTA variables to map into your merge fields.
Document Creation (Word Document from Word Template)
The primary KTA functionality relevant to your goal is the Document Creation activity (under "Other" when choosing activity type). You will want to read the help topics for a full understanding of the options, but it will allow you to map variables into merge fields from a Word Template (dotx).
The configuration interface of the activity does not make this immediately apparent, but the Document Save Location can be a document variable instead of a path. Once you provide a document variable, the interface will expand to also allow you to choose a folder variable to which the document will be added. Then you can map your data from variables into the merge fields.
Create and Export PDF
Note that using a document variable for the Document Save Location, rather than a file path, is essential because PDF generator works on Document/Folders within KTA, not file paths.
After your Document Creation activity, you can add an Image Processing activity (to convert the merged Word document to tif), and then a PDF Generator activity to create your PDF. Use an Export activity to export the PDF to the location of your choosing.
I think PDF Generator requires tif pages be created first, but you could try sending the Word document without the IP activity if you
want to confirm.
I'm working with SPARX Enterprise Architect (version 11.0), and as part of a larger model I am modeling requirements. I've created a bunch of Requirement entities, but I would like to export them as some sort of table into a word document.
Is there an easy way to do this? I've tried using the "templates" in the past, but they're rather complicated and they spit out a lot more than what I'm really trying to export.
If you want to create a Word document out of native EA, document templates is all you've got. However, you can export model data as CSV, import it into Excel and from there to Word.
There are several ways to export CSV data from EA, ranked from hardest-but-most-reusable to easisest-but-most-manual:
Create a CSV import/export profile and run it (project browser context menu -- Import/Export -- CSV Import/Export).
Create a search which finds the elements, run it and copy from the search results window into Excel. The search defines which columns are created.
Place the elements in a diagram, switch to list view (diagram context menu, or diagram main menu -- Show Diagram As -- List View) and copy from that. The columns can be selected by right-clicking a column header.
You can
Create a document generation template, which you can tailor so it only reports what you want it to.
use the model search and copy/paste the contents into a .CSV file. If you create an SQL search you can define exactly which fields are shown int he search results.
Create a CSV export profile where you define which fields to export in which order.
If you are not satisfied with the options offered by Enterprise Architect, you might want to give "eaDocx" a try.
eaDocX™ is the Microsoft Word and Excel document generator Add-In for Enterprise Architect
I am new to stackoverflow because I almost never ask questions in forums as there are plenty of questions out there already answered. However my head is about to explode from trying to figure out how to do this app.
First I do this using XCode 4.5.2 for OSX 10.8 deployment of a personal (that is for my use only) double entry accounting software.
Each accounting entry consists of a header of various text fields such as the entry date, a serial number, etc. which I created an Entity called "Entry". Also each such entry has multiple lines such as the various accounts related to that entry, amounts, etc. called an Entity "EntryLine" linked in the model nice and easy.
The thing is that I intended to use text field for the basic header info and below it a linked Table View for each of the line. Being an accounting software there are several checks (validations) that I need to make and I need full control of what is going on. Already tried binding two array controllers, one for each entity and linking the two and saving them to the sqlite file but to no avail!
Now I have an app with just the header up and running by manually getting and setting the info in the top text fields as I please and saving them to the file. But I have no idea how to do the part with the Entry Lines in the Table view. Can I do that manually too or is it better to do bindings through an array controller?
Also tried already with array controller but I get "Table View Cell" when I add a new line in the table. Any ideas on that?
In the Table View there is also an "Account Name" part that is NOT part of the EntryLine entity but my intention is to obtain this information from another entity called "Account" that stores the Account Number and Account Name. On input of the account number that is, the app would skip the name field and move to particulars for input but also bring up the name of the account already inputted. Is this even possible?
Sorry for being a bit vague in my questions but I come from routine program oriented languages and not object oriented one, though I have some Java experience. Any help would be appreciated. No screenshot sorry as I am not yet allowed:(
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.