I'm seeing some odd behaviour deploying a package built on a T1/CHE build box and hoping folks can please offer some thoughts. The package contains 6 VAR models, and we have a continuous deployment pipeline in ADO that uploads the package to LCS then triggers deployment to a T1 'test' box (which has only ever had deployable packages applied, never been used as a dev box. The first deployment always fails, but if I manually apply the same LCS asset, it succeeds. Same behaviour on another T1 environment I provisioned just to investigate, so I don't think it's intrinsically anything to do with the T1 box, but something about the package. So, I've tried a full build of all VAR models on an actual dev box: no issues. A colleague suggested that the full deployable package will include some checking of referenced packages, so I've tried a build of the models & reference models on the dev box: no errors during compile, but dbsync now gives an error on a standard view. Based on the label reference in there, I would have said something to do with Supply Chain Management, but when I search for @SCM references in K:/AOSService, most of them appear in the ApplicationSuite model folder.
CREATE VIEW [DBO].[TAMVENDORREBATEAGREEMENTPRODUCTSELECTIONV2ENTITY] AS SELECT T1.INVENTDIMID AS INVENTDIMID, T1.ITEMID AS ITEMNUMBER, T1.VENDREBATEAGREEMENTREFRECID AS REBATEAGREEMENTREFRECID, T1.UNITID AS PRODUCTUNITSYMBOL, T1.RECVERSION AS RECVERSION, T1.DATAAREAID AS DATAAREAID, T1.PARTITION AS PARTITION, T1.RECID AS RECID, T2.VENDREBATERELATION AS VENDORACCOUNTNUMBER, T2.RECVERSION AS RECVERSION#2, T2.DATAAREAID AS DATAAREAID#2, T2.PARTITION AS PARTITION#2, T2.RECID AS RECID#2, T3.CONFIGID AS PRODUCTCONFIGURATIONID, T3.INVENTCOLORID AS PRODUCTCOLORID, T3.INVENTLOCATIONID AS QUALIFYINGWAREHOUSEID, T3.INVENTSITEID AS QUALIFYINGSITEID, T3.INVENTSIZEID AS PRODUCTSIZEID, T3.INVENTSTYLEID AS PRODUCTSTYLEID, T3.RECVERSION AS RECVERSION#3, T3.DATAAREAID AS DATAAREAID#3, T3.PARTITION AS PARTITION#3, T3.RECID AS RECID#3, (CAST ((@SCM:SqlFieldStringFormat) AS NVARCHAR(20))) AS REBATEAGREEMENTID, CAST(NULL AS NVARCHAR(10)) AS PRODUCTVERSIONID FROM TAMVENDREBATEITEM T1 CROSS JOIN TAMVENDREBATEAGREEMENT T2 CROSS JOIN INVENTDIM T3 WHERE(((( T1.VENDREBATEAGREEMENTREFRECID = T2.RECID) AND ( T1.DATAAREAID = T2.DATAAREAID)) AND ( T1.PARTITION = T2.PARTITION)) AND ((( T1.INVENTDIMID = T3.INVENTDIMID) AND ( T1.DATAAREAID = T3.DATAAREAID)) AND ( T1.PARTITION = T3.PARTITION))) | SQL Exception Number - 137 - System.Data.SqlClient.SqlException: Must declare the scalar variable @SCM.
Any thoughts appreciated: I've now got a somewhat broken dev box, and still have my confusing /first deployment fails, second deployment succeeds/ behaviour. The ADO pipeline history looks like all releases have failed, when they succeeded with a little persistence :)
