Skip to main content

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:       UsedInActionInput = true,  
15:       UsedInActionOutput = true,  
16:       UsedInLookupCondition = true,  
17:       UsedInQueryConstraint = true,  
18:       UsedInQuerySelect = true,  
19:       UsedInQuerySequence = true  
20   }

Here I want to note lines 12 and 13.  Set these to the value types that your list will contain.  In this case we will have a list of strings.

2) Publish connector so you can use it in SCRIBE Online.
3) Create your mapping and for this attribute use the TOLIST() function.  It can be found in Functions -> Conversion -> TOLIST().

This function takes 6 arguments all separated by a comma.
1) The list of items. Example "ABC123, DEF456, GHI789" - Here you can use a function to read from a source instead of typing in all the data.
2) The delimiter we used to separate the list. Example ","
3) The type for the data.  Example "string"
4) How to sort the data.  Example "a" for ascending.
5) Do you want to remove quotes?  Example true.
6) Do you want to remove empty values? Example true.

Here is the expression completed with the examples above:
 TOLIST("ABC123, DEF456, GHI789", ",", "string", "a", true, true)

Here is the output:
 "EntityIDs":   
 [  
   "ABC123",  
   "DEF456",  
   "GIH789"  
 ]
Labels:

Comments

Post a Comment

Popular posts from this blog

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if ...
22 comments
Read more

Reusable Method To Get Record By Id

I have a handful of reusable code that I use when creating plugins or external process (i.e. Azure Functions) for working with DataVerse. The first one I am providing is Getting a Record By Id: 1: private static Entity GetFullRecord(string entityName, string primaryKey, Guid recordId, IOrganizationService service) 2: { 3: using (OrganizationServiceContext context = new OrganizationServiceContext(service)) 4: { 5: return (from e in context.CreateQuery(entityName) 6: where (Guid)e[primaryKey] == recordId 7: select e).Single(); 8: } 9: } entityName = The logical name of the entity primaryKey = The primary key field for the entity. If using late binding you can create this dynamically by doing: $"{target.LogicalName}id" recordId = Guid of the record to get service = Service to interact with DataVerse
4 comments
Read more

Understanding Managed and Unmanaged Solutions in Dynamics 365

Dynamics 365, Microsoft's robust suite of business applications, boasts a myriad of features that can be customized to cater to the specific needs of any business. A vital concept to grasp when working with Dynamics 365 is the difference between managed and unmanaged solutions. This blog post aims to clarify these two types of solutions, providing a comprehensive analysis of the advantages and disadvantages of each. Unmanaged Solutions Unmanaged solutions act as a dynamic development environment, enabling direct alterations and additions to system components. They are often employed during the development and testing phase of a customization project but are equally effective when implemented in production instances, particularly for internal organizational operations. Pros of Unmanaged Solutions: Flexibility : Unmanaged solutions provide a high degree of adaptability, permitting developers to modify system components, introduce new elements, or discard those that are no longer nece...
3 comments
Read more