Jeff Levetin

Hi @Kirill Yunussov, We identified and resolved the issue, and are currently monitoring. The email notification from our trust site went out a few minutes after your post. You can see the current status and sign up for notifications at: https://trust.scribesoft.com/ Please submit a ticket if you're still having an issue.

@Dan Haas - please submit a ticket.

Hi @Dan Haas, Other things to try: If you are using an on premise data store, double check that the solution is using the correct on premise agent and not a Cloud agent. Create and use a new connection and a new solution Reset the Meta-Data from within the map, save, and open after a few minutes If a Cloud agent, delete the agent and create it again, if they're aren't already solutions using the Cloud agent. It's also possible the On Premise agent is on a slow network and not communicating with the TIBCO cloud services. If the end point is in the Cloud, use a solution with a Cloud agent and add just your connection. If that works and the on-premise agent doesn't, it's probably related to the on-premise agent environment. If you're still having issues after all that, please submit a ticket.

Hi @Dan Haas, Sometimes this is caused by a slow metadata load. Try resetting the metadata from the connections page and wait a few minutes. From the menu, More, Connections. Mouse over right most column to expose the gear, click and select Reset Metadata. For endpoints with lots of entities, it may take a while for the initial load to finish.

Hi @Don Panek, There are a couple options: Option 1 - Move the file after the map runs (preferred): Configure the integration to move the file to another directory after post processing. This is done in the connection properties for the Text File as a Source connection. See the section Post Processing Rule in: https://help.scribesoft.com/scribe/en/#sol/conn/text_entities_tab.htm Option 2 - store SHA1 hash in 3rd party database: You can use the Scribe Labs - Tools connector to generate a SHA1 hash of the data. Use the Execute block, entity SHA1, field InputString. CONCATENATE() all fields. You'll need to store this in a 3rd party database. You might be able to use a LookupTable through the Scribe Platform API connector. Beware of API usage and table size. The would probably only work with a small data set in the range of thousands. For each record, hash the data, lookup the hash value in the datastore. If found, skip, else process the record and add the hash it to the datastore. Hope this helps.

Hi @Ramy Zahran, You can use the Scribe Labs - Filestream connector with an on premise agent. Install an on premise agent Create a directory to hold the files on the same server as the agent (i.e. D:TIBCOIntegration Under Marketplace, Activate the Scribe Labs FileStream connector Create a FileStream connection, use the directory from above (i.e. D:TIBCOIntegration). Call it FileStream In the map, add the connections for Salesforce and FileStrem Query the Salesforce Entity to get it's id field Use the FileStream block ReadFile, entity "file." Put the full path of the file you want to upload in the "filepath" field. Use the Salesforce Create Block, entity "Attachment". Map the result field FileStream_fileReadFile.filedata to the Body field. Here's a sample map: And here is how the field mapper looks for the Create Attachment block: Remember that the FileStream connector is part of TIBCO Scribe labs and is not officially supported.

Hi @Patrick McLeod You need to create an Integration Solution (IS), not a Replication Solution (RS). Then add the map to the Integration Solution.

Hi @Patrick McLeod, I don't see the screenshot images. I think you need to attach the files using the image icon at the bottom. I don't think cut and paste works. Jeff

Hi Patrick, Here are the steps: Install an agent Cloud if both tenants are in the cloud, or an IFS On Premise if one of the tenants is on premise Note: you won't be able to migrate data between 2 on premise only installations Create two connections, one for each D365 instance Create a Solution and select the appropriate agent Create a Map within that Solution Add the connection for the source Add the connection for the target Drag a Query block from the source Select the entity and any filters Drag a "For Each Result" and link to the Query Dray the needed Create, Update, Insert, or Upsert Block Select the entity Enter match criteria if an Update block Map the fields If you're migrating data from one D365 instance to another, you'll have to implement the appropriate key matching, GUID re-use, status changes, etc. Hope this helps.

Hi @SasiKumar Natesan, A text file can be hosted locally like in D:Source, or in a Cloud endpoint like FTP or Dropbox. For a local file on a windows machine, you need to install an on premise agent on the same machine. If you already have an agent installed, change it on the Solutions edit page at the top right. Otherwise you need to install an agent on that machine. Note that if you plan to use a directory other than the default /Dataexchange, you need to add D:Source to the FolderAccess.txt file: ("C:Program Files (x86)Scribe SoftwareScribe Online AgentConnectorsScribe.Connector.Text.SourceFolderAccess.txt")

As I understand, there was a resolution for this question. Salesforce Contracts so do not have Line Items. Service Contracts (which is a different record type entirely) do allow for Contract Line Items and the connector does support "Child" relationships for these as long as you have the right settings turned on within Salesforce. Also, to answer part of your original question, you can use a Fetch block to retrieve child records, whether or not a declared relationship exists. https://help.scribesoft.com/scribe/en/index.htm#advsys/maps/blocks/fetch...

Hi @Nelson Johnson, Openmind was retired and is now read only. Please use the link on the bottom of this page to open a case for Insight: https://success.scribesoft.com/s/ Jeff

Hi @James Studer, Great work. I created a similar function, but your's is more elegant.

Hi @Adeyemi Lawal, You're correct that it's expecting an integer type. But you can map a string to the field, as long as it is one of the options.

Hi @Adeyemi Lawal, With Scribe Online In CRM, you can map the label value / display name directly into the picklist numeric field. province: sqlentity.province For CRM to CRM mappings: In the Connector parameters, check "Include Picklist Display Names" In the Create or Update block, map the _displayname to the field. Here's an example statecode: contact.statecode_displayname If the displayname is not valid, it will throw an error. Other options: Store the integer value mappings in a .csv file and use CSVLOOKUPVALUE (for on premise agents) Use a Lookuptable for cloud agents Use the function CHOOSEBYVAL()