My decide shape is not working correctly


hi,

i have created simple orchestration should split files 3 different folders. splitting done looking in .xml specific number.

so created variabele in orchestration , created expression shape , under 3 rule branch decide shape.
in expression shape created next expression: variabelestring = msgncts.declaration.reference.  variabelestring variabele , msgncts.declaration.reference message.

so in decide shape have 3 branches split files folder 1, folder 2 or format isnt recognized folder 3 (else).
in first branch created expression: variabelestring.substring(0,1) == "1" checks first number of distinguished property.

in second branch expression is: variabelestring.substring(0,1) == "2"

when test application first branch works perfectly, files have numbers like: "1 096608/40/bn000418" , "1 01113/10/bn000765".
else branch working correct, other files redirected correct folder.
problem second branch, should redirect files second folder if files contain number like: "2 096608/40/bn000418" , "2 016408/60/bn000875". aint working, files started 2 ends in folder 3, else folder.

when manually adjust reference number in file "2 096608/40/bn000418" "2" , test application file goes folder 2 should be. know goes wrong in application?

 

 

hi

i have worked allot decide shape never observed problem this. think cause of might value being parsed different. may can debug writing event log in expression shape. , should able debug out using event viewer.

            system.diagnostics.eventlog.writeentry(variabelestring.substring(0, 1));


BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more