Skip to main content

XrmToolBox Bulk Attachment Manager - Version 2018.2.2.7 Released!

Today I have published version 2018.2.2.7 of my XrmToolBox plugin.  The purpose of this plugin is to make it easy to download and backup attachments in CRM.  This release is a major release as it is the first built version with all pieces working.  The first version only had note downloads working.

Overview of Plugin:
How To Use The Tool:
  1. Launch XRMToolBox.
  2. Connect to organization.
  3. Step 1, choose what you want to download. (Once a choice is made, Step 2 becomes usable)
    1. Notes - Download attachments from note entity.
    2. E-Mail - Download attachments from emails.
    3. Both - Downloads attachments from notes and emails entities.
  4. Step 2, choose if you want to download all attachments in the system or specific attachments.  
    1. All Attachments - This will search the chosen entity to find all records that have an attachment and download them.
      1. Click on "Browse" and choose where to download the attachments too.
    2. Specific Attachments - You will need to provide a .csv file with a GUID(s) of the records you want to download.
      1. Click on "Browse" and choose the .csv file to use.  Attachments will be downloaded to the same location as the .csv file.
  5. Step 3. click on "Run".
  6. When complete, in step 4 click on "Export Results".  This will export the data in the output area into a pipe delimited (|) .csv file.
Notes:
  • Note attachments are stored in a "Note Attachments" folder at the download location chosen.
  • Email attachment are stored in a "Email Attachments" folder at the download location chosen.
  • Inside the folder mentioned above are other folders.  The folder for each of these sub-folders is the GUID of the source record (Note / Email).  This way we can maintain the relationship of the records.  Within this folder are the attachment(s).
If you run into any issues with this plugin please report the issue against the GitHub Project.

Comments

Popular posts from this blog

Dynamics 365 v9 Unit Testing and .NET Confusion

Recently while creating a plugin for Dynamics 365 v9, I ran into an issue trying to connect to CRM via the tooling connector in my unit test project.  The underlying problem was that the .NET version I was using in my unit test was 4.5.2.  This was preventing me from being able to connect to CRM to create my organization service.  I updated the .NET version on my unit test project to 4.6.1 and was then finally able to connect.  I will also add that I am using the latest nuget package version for Dynamics 365 v9.

For consistence, I updated the plugin project I was working on to .NET 4.6.1.  Locally, everything was working great.  I was able to connect to CRM and make sure that all the methods I had written did what they where suppose to do using test driven development practices.

Then when publishing my plugin via the latest version of the plugin registration tool, I received an error and could not publish my plugin.  The error was due to the .NET version of my plugin project not bein…

SCRIBE Connector Development - Handling Array List

Are you working on creating a connector with SCRIBE's CDK?  In your connector do you have an array of strings or list of  strings that you need to pass?  SCRIBE makes this easy to do within the CDK and SCRIBE Online.

I came across this scenario on a connector I was creating that passes a JSON message to an API.  In the JSON message it had a list of strings for entity ID's. Here is an easy way to accomplish this:

1) Create you Property Definition as past or your Object Definition.
1: new PropertyDefinition 2: { 3: Description = "Use TOLIST() to pass in a list of entity id's.", 4: FullName = "Entity IDs", 5: IsPrimaryKey = false, 6: MaxOccurs = 1, 7: MinOccurs = 0, 8: Name = "PublishTo", 9: Nullable = true, 10: NumericPrecision = 0, 11: NumericScale = 0, 12: PresentationType = "string", 13: PropertyType = typeof(string).Name, 14: Use…

Getting Started Connector Development

One of the benefits of working with Scribe Online is how easy they make it to create connectors if one does not exist.  In this blog post we are going to look at how to get setup, if this is the first time you have made a connector for Scribe Online.  But, before we get into that, we should first make sure that a connector doesn't already exist that can handle what we need.

We can do this by looking in the Scribe Online Marketplace.  Still not seeing what you need?  Reach out to Scribe directly or ask in the Scribe forums if a connector exists for an application.  There are instances where a connector exists but is not listed in the marketplace.  An example of this is for a client that I built a connector for.  They didn't want to setup a system to run the on-premise agent, so they asked me to set up the connector to run on Scribe's cloud agent.  This meant that I had to submit the connector to Scribe for validation.  Once published the connector is in the Scribe marketpla…