Hi If you need to build more complex SQL Lookup you can use the "Parameterized SQL" node, ie Select description from mylist where id = ? and version = ?". Next the parameters have to be passed in the exact same order. ... View more

Can anyone please confirm if the below SQL procedure is good. We are getting the below error when we call this SQL procedure from SAS MDM Dataflux job.   2019-07-31T08:57:47,916 ERROR [ROOT][53A9AEFD4BDBEE9E_JOB_7_0][539E8D0EF9C1EC5D_JOB_13_0][DATAFLOW_10_0]Node DATAFLOW_10 error: [1:EXPRESSION:Start Process Control] Expression Plugin - [25000] [DataFlux][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. (3903);[25000] [DataFlux][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.   Below is the stored procedures, when i checked the syntax of these, i dont see any issue, could you please check it for me?   USE [SASMDM]; GO SET ANSI_NULLS ON; GO SET QUOTED_IDENTIFIER ON; GO CREATE PROCEDURE [sasmdm].[mdm_start_process_control] ( @parm_staging_id INT, @parm_entity_type_id INT, @parm_src_sys_id INT, @parm_process_name VARCHAR(50), @parm_process_type VARCHAR(50), @parm_user NVARCHAR(513) ) AS BEGIN SET NOCOUNT ON DECLARE @process_id INT EXEC @process_id=[mdm_start_process_control_next] @parm_staging_id,@parm_entity_type_id,@parm_src_sys_id,@parm_process_name,@parm_process_type,@parm_user select @process_id as process_id END GO     --------------   USE [SASMDM]; GO SET ANSI_NULLS ON; GO SET QUOTED_IDENTIFIER ON; GO CREATE PROCEDURE [sasmdm].[mdm_start_process_control_next] ( @parm_staging_id INT, @parm_entity_type_id INT, @parm_src_sys_id INT, @parm_process_name VARCHAR(50), @parm_process_type VARCHAR(50), @parm_user NVARCHAR(513) ) AS DECLARE @timestamp datetime; DECLARE @process_id INT; SET NOCOUNT ON BEGIN TRY SELECT @timestamp = GETDATE() BEGIN TRAN INSERT INTO [MDM_PROCESS_CONTROL] ( mdm_staging_id, mdm_entity_type_id, mdm_src_sys_id, process_name, process_type, process_running, process_user, process_start_dttm) VALUES (@parm_staging_id, @parm_entity_type_id, @parm_src_sys_id, @parm_process_name, @parm_process_type, 'Y', @parm_user, @timestamp) COMMIT TRAN SELECT @process_id = process_id FROM mdm_process_control WHERE process_name = @parm_process_name AND mdm_entity_type_id = @parm_entity_type_id AND mdm_staging_id = @parm_staging_id AND mdm_src_sys_id = @parm_src_sys_id AND process_running = 'Y' AND process_start_dttm = @timestamp; RETURN @process_id END TRY BEGIN CATCH ROLLBACK TRAN DECLARE @error_messages VARCHAR(2000) DECLARE @errorSeverity INT DECLARE @errorState INT DECLARE @errorStatus INT DECLARE @errorProc VARCHAR(150) DECLARE @errorDate DATETIME DECLARE @mdm_error_status VARCHAR(10) DECLARE @mdm_error_messages VARCHAR(4000) DECLARE @errorSeverityString VARCHAR(100) DECLARE @errorStateString VARCHAR(100) SELECT @errorStatus = ERROR_NUMBER() SELECT @error_messages = ERROR_MESSAGE() SELECT @errorSeverity = ERROR_SEVERITY() SELECT @errorState = ERROR_STATE() SELECT @errorProc = ERROR_PROCEDURE() SELECT @errorDate = getDate() SELECT @errorSeverityString = CONVERT(VARCHAR,@errorSeverity) SELECT @errorStateString = CONVERT(VARCHAR,@errorState) SELECT @mdm_error_status = CONVERT(VARCHAR,@errorStatus) SELECT @mdm_error_messages = @errorProc+ ' : '+@error_messages+ ' : '+@errorSeverityString+ ' : '+@mdm_error_status+ ' : '+@errorStateString -- Log Error EXEC [mdm_log_error] 'MDM_PROCESS_CONTROL',null,0,null,'mdm_start_process_control_next',@mdm_error_status,@mdm_error_messages,@errorDate -- Raise Error RAISERROR(@error_messages, @errorSeverity, @errorState) END CATCH GO ... View more

Hi For listing all the business rules you can use the "Repository Info" node. If you want to get the rules and the tasks that are associated with jobs, then you will need to have the data governance capabilities, especially the process job allowing to export relationships (pj_export_lineage).   Vincent ... View more

Hi If not already submitted,would suggest to open support track by SAS Tech Support and to add log file. Mind that mrm data services are designed for being used by SAS MDM web interface. ... View more

 Hi   By SAS Data Management console, do you mean Data Remediation, MDM or Visual Process Orchestration? The former will be available in HTML5, but the later will be only supported through fat client. In addition, we are working on a set of VA reports that will be proposed as a Home page for SAS DM products. Again, we are having many conversation with SAS DM Customers about FLASH eol, I will recommend to contact your SAS sales account team, for getting more details and info about impacts.   Vincent   ... View more

I've been dabbling with this, and hit the fundemantal issue that JSON is inherently schema-less, unlike XML. Essentially, you are never sure what you're going to get, in terms of field structure, from any one REST call (or another expression of data in JSON, like an "export to file").   What I tried was creating "template" datasets/tables, that I could use to conform any instance of JSON derived tables (from the same source or endpoint) to the virtual schema that the data (more or less) complies with.    So in the code I was working on, once I've got the various tables - but often only one really - back from the JSON library, I run them through an append to an empty "target instance" of the template dataset, freshly created for the purpose of being the output from my user transform, which means that I get an output table from my call to the REST end point that's crudely conformed to a static structure/schema.   I ended up with a User Transfrom that took the "template" dataset as an input, and the REST endpoint details and options/parameters as options, and coughed out a dataset with a fixed format. So in DIS, I could use registered tables as the output of the UT that called hte REST endpoint, with a stable data structure.   PROC APPEND is a but low-tech/brute force for doing this, it would probably be better done in a more in-depth macro. There are options to suppress the squawking about the JSON sourced table not being just like the template derived BASE, but I couldn't get it to stop issuing warnings, and "probably beneign warnings" are absolutely not what want in a DIS UT.   XML is much prefereable, as the XML Map mechanism, and XML itself, tackles the issue of how to handle parts of a schema not being present in a particular set of records - in JSON the absence of a schema, and the absence of any sort of placeholder for "not present" data items/fields, means that it's actually an undesireable format for "ETL-esque" data transport, but it's not going away. ... View more

Hi @VincentRejany, In order to check that my depot has SAS Metadata Bridge Content Types, i should navigate to <depot location>/install_doc/<order number>/ordersummary.html and check if it has SAS Metadata Bridge Content Types 4.2 listed. Am i right? Thank you in advance ... View more

Hi Vincent,   thanks for your replay. I tried your code but unfortunately I got an error massage.       I made some negative-tests and I think my dataconnection is fine and my list has also entries. Any suggestions what the error caused?        ... View more

Hi   The log shows Process Flow - Job terminated due to error in one or more nodes, because you generate an error when interrupting the process. For your second question, would suggest to open a ticket by tech support.   Regards ... View more

Hi   SAS Metadata Bridges are traditionnaly deployed with SAS Data Management products. SAS Data Integration Server includes the SAS Metadata Bridges for General Industry Standards and a choice of 3 additional bridges. Solutions that include SAS Data Integration Server also include the Metadata Bridges that come with the DI Server.   Hope that helps   Vincent ... View more