Does the output from WEX support the entity type roles based on context from WKS? - watson-knowledge-studio

If I prepare a machine learning model in Watson Knowledge Studio annotating using entities types with roles based on the context, will these entities types with roles appear in the reports and exported output from Watson Explorer (oneWEX) ?

Currently entity roles will not be used as a facet when using your model created by WKS as annotator with other services like Watson Explorer generally.
Thank you.

Related

PowerApps - what could be licensing requirement for me to create entities in CDS?

I exported a SharePoint list to Excel and then tried Data -> Entities -> Get Data to create entities in CDS uploading data from Excel. It says 'You are missing privileges to create entities in this environment.' What could I do?
Possibilities of this error while creating entity are:
You are trying to create entity in some environment where you don't have security role/privilege to do this operation, viz Environment Admin, System Admin, System Customizer or custom Admin role
Trying this operation in Default or a CDS environment without database provisioning (highly unlikely)
Probably you have Environment maker role, client assumes that it is enough which is not the case
Try to get Admin privileges in Dev/sandbox environment from your client or create a trial org to try out things. You may have license but the basic role to access the system as an end user will not help you to do such stuffs.

Problem retrieving Dynamics CRM custom fields for integration in ADF

I am doing data integration from Dynamics CRM to Azure SQL Database using Azure Data Factory. I am unable to fetch the custom fields
created in Dynamics CRM for doing the mapping in integration. Please help me with the solution for the above.
We ran pretty hard into the limitations of the Dynamics connector of Azure Data Factory v2. The ADF Dynamics connector does not expand the fields and requires a way too big rewrite of our current logic. Either with an entity selection or FetchXML, same results.
We were using SSIS + Cozyroc that did expand a lot of fields automatically. So we are back to using SSIS + Cozyroc. And since running custom components on SSIS-IR is... challenging we are also back to running SSIS on-premise.

Scribe Insight: Migrate Principal Object Access table data from CRM 4.0 to CRM 2016

I am using scribe to migrate the Principal Object access data from CRM 4.0 to CRM 2016 DB.
The source adapter is a SQL Data Adapter which reads the data from the POA table in 4.0.
The destination adapter is the CRM Adapter and I have an insert step to insert the data into CRM 2016.
In the destination adapter, Scribe does not allow me to add the data links to PrincipalId and ObjectId fields from the source.
As far as I know, both of these fields are required to create a principal access object. However, since I can not create the data links, I do not know how I can copy this data over to CRM 2016.
Has anyone ever tried to Migrate the Principal Object Access table using scribe and have any suggestions for me to try out?
Any help will be greatly appreciated.
A few things I've noticed from your screenshot that might help you out:
You're trying to set the principalobjectaccessid on insert. I would think this is a no-no as you are creating a crm record and want a new guid to be assigned at that time instead.
You're doing the lookup to the type code but not to the foreign keys for the objectid and the principal id. You would need to refer to those (probably by name or an xref table as the guids will be different post import) in order to get the sharing in place.
In order to lookup those objects and principals you will need them to be entered into CRM2016 in a prior step.
One caveat I'd add is that based on the limited knowledge I have of you trying to move a 4.0 thought process involving sharing over to CRM 2016 this very well could be a bad idea. While sharing is still supported and certainly a part of the application there's performance issues that come up with extensive sharing and it's honestly a much more complex thing to work with then utilizing teams.. As I'm sure you're noticing now.
The POA table is internal to CRM and shouldn't be written to directly, even via the API.
It stores details of how records (determined by the objectid) are shared to users/teams (determined by principalid).
It sounds like you want to migrate your shares from CRM 4.0 to 2016. Scribe has a mechanism for doing this, using virtual fields. Look in the help for "Adapter for Microsoft Dynamics CRM" and search for "Granting Access". This explains how to use the virtual fields.

How to create entity class from synonyms in oracle?

i can create entity class from available tables but i want to create entity from synonyms in my oracle which are not showing in my table list...
(i have used eclipse JPA tools to create entity class)
how to see synonyms and create entity
Whether Dali (the Eclipse plug-in that provides these JPA tools) can see and use table synonyms depends on the DTP extension you are using to access your database's metadata. If your synonyms show up in the Data Source Explorer under your database's "Tables" folder, they should show up in the Entity Generation wizard's list of tables. If they do not also show up in the wizard, that is a possible bug.
Note: There are some third-party extensions that do not want Dali to use synonyms. You might look at this bug from a few years ago: https://bugs.eclipse.org/bugs/show_bug.cgi?id=288027

Populating a Visual DSL with database information

I have the following problem to solve:
Currently we have a metadata tree of the databse schema that has a in-memory representation and a proprietary schema XML serialization as well (that is we can read/write all the in-memory data to an xml file).
Currently I am developing a Visual DSL solution (diagram-like), to allow easier operations with the datbase schema and need guidance in the following:
I want to populate the DSL model from the metadata tree that contains the database schema information, and I am not sure which is the best way (I am new to DSL so I am not sure whether I see all the possible ways of doing it). So far I know of the following:
On creating the DSL item in Visual Studio, I fetch out the schema creating a metadata tree, then I serialize it to a the DSL's XML schema inside the DSL file created for the new item. That way when the DSL is opened it will deserialize correctly. However this requires a lot of code to translate our own data to such required by the DSL.
I would like, if possible to instantiate a metadat tree, to traverse it, changing the dsl model at the same time through code/API.
So any guidance into that direction (the way you are doing it) will be valuable for me.
You might try asking the DSL forum on MSDN: http://social.msdn.microsoft.com/Forums/en-US/dslvsarchx/threads

Resources