Logic Apps

Logic Apps allow developers to design workflows that articulate intent via a trigger and series of steps, each invoking an App Service API app whilst securely taking care of authentication and best practices like durable execution.
If you have any feedback or ideas on Azure Logic Apps we’d love to hear it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Office 365 Connector Ignores .msg (email file) attachment in incoming Emails

    The bug is with the Office 365 connector when triggering on new incoming email.

    The issue is when the incoming email contains a .msg file, or Outlook item, as an attachment (read, email has an email as an attachment).

    What I am experiencing is that the connector correctly sets "Has Attachment" as True, even when the email object is the only attachment, but the "Attachments" output is empty.

    When the .msg is the only attachment the output reads as

    "Attachments":[]

    While the .msg attachment is directly ignored from the "Attachments" list if more attachments are included in the incoming mail.

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. OneDrive / OneDrive for Business Connector 'When a file is created' event not always firing

    I have a Logic App which uses the OneDrive for Business Connector.

    With the 'When a file is created' event, if I specify the root folder ('/') as the Folder property, then upload a file to the root folder, it works fine.

    If I specify any other value, it doesn't fire, and is 'Skipped' in the History tab in Azure Portal.

    The folder I'm wanting to observe is called 'Transcripts'; I have tried:
    * /Transcripts (this is what gets populated if I use the folder picker in Logic App Designer in VS2017)
    * /Transcripts/
    * Transcripts/
    * Transcripts

    This seems…

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Issue with SQL API connector - Some of the connections are not authorized yet.

    I am copying the same issue from another person. This seems to be a new bug.

    My flows connecting to Azure SQL stopped working today as the lost the SQL connectoin I set up. Trying to set the sql connection again I get below error.

    Some of the connections are not authorized yet. If you just created a workflow from a template, please click Continue to add the authorized connections to your workflow before saving.

    I tried re-adding connection multiple times, but can't get pass this

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. Email alias not triggering action

    Hi,

    The initial action within my azure logic app is:

    Office 365 Outlook - When a new email arrives.

    If I put an alias into the TO: field the action is not fired.

    If I put my email address into the TO: field the action is fired.

    I've confirmed the alias is operational by sending/receiving an email.

    Regards,
    Graham

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. OneDrive trigger is not coordinating file contents

    In the case other than the txt file, the value is returned as the content in the form of JSON which is thought to be used internally, not the file binary.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Issue with SQL API Connector

    When trying to add a SQL connection in my Logic App, I enter the connection string details but then it throws the following error:

    Please check your account info and/or permissions and try again. Details: Argument out of range
    inner exception: Index and length must refer to a location within the string.
    Parameter name: length
    clientRequestId:

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Bug in Logic App connector to create automation runbook job with boolean parameters

    I have a Logic App that has an "Azure Automation - Create Job" action. This action calls a runbook to fire off some powershell commands to do some tasks to the data warehouse.

    I also have a parameter that the Powershell runbook accepts. That parameter is a Boolean value.

    The Logic App connector that calls the automation runbook has a field for parameters. This connector will pass variables to the runbook, HOWEVER, when passing Boolean values, the connector will only allow "true" and "false", but these are NOT valid values for powershell Boolean values.

    Powershell expects $True, $False, 1 or…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Can't edit a compose action in the designer - edit disappeared?

    Hi,

    The advanced edit for a compose action has disappeared from the Azure Logic Designer?

    See attached picture.

    The only workaround is to edit or peek the code.

    "Condition_-_was_a_pdf_attached": {
    "actions": {
    "For_each_2": {
    "actions": {
    "Compose": {
    "inputs": "@concat(utcnow('yyyy'), '/', utcnow('yyyyMMdd'),'/', triggerBody()?['Id'], '/', items('For_each_2')?['Name'])",
    "runAfter": {},
    "type": "Compose"

    Can the option be put back int the designer?

    Regards,
    Graham

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. AS2 Decode won't fail when message is not signed and encrypted

    I've configured an AS2 agreement with receive options : "Message should be signed" and "Message should be encrypted" set to true.

    When I post a message without signing and encrypting the request, the AS2 Decode action is suceeded but I thought this should be failed.

    In the action output, I can see the following properties :

    "dispositionType": "failed/failure: decoder-party-signing-configuration-error Error: Configuration error. The message signing doesn't match the expected value. Contact the sending partner and verify signature use. AS2-From:\"***\" AS2-To:\"yyy\" MessageID:\"zzz\""

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. SharePoint Online - When an existing item is modified - MMS Column Failure - Bad Gateway

    Steps to reproduce:

    1) Add 'When an existing item is modified' trigger to a new Logic App or Flow.

    2) Target list has MMS column where internal name is different to display name - a display name with spaces ('Company Name'), and an internal name without ('CompanyName').

    Result: On run, Bad Gateway: status 502, message "Unknown Error", source "<URL>/_api/SP.APIHubConnector.GetUpdatedListItems".

    Does not appear to happen with other types of field (e.g. text, lookup). Does not seem to depend upon term set title.

    Workaround: create columns where the internal name and display name are the same.

    Why this is bad: it encourages…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  11. List Blobs

    "List Blobs" Action cannot find the blobs in the mentioned Container.
    The blobs do exist in the Cointaner.Seems like a bug as it has worked fine till Dec 2017.

    "body": {
    "value": [],

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. Logic Apps AS2 encoding incorrectly creates a base64 MIME part without line breaks

    A signed AS2 message, generated by the Logic Apps AS2 encode action, looks something like:

    Content-Type: multipart/signed;
    protocol="application/pkcs7-signature";
    micalg="sha1";
    boundary="_48c45571-a0d0-49cc-b980-72e58e45eb46_"

    --_48c45571-a0d0-49cc-b980-72e58e45eb46_
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: binary
    Content-Description: body

    <test/>
    --_48c45571-a0d0-49cc-b980-72e58e45eb46_
    Content-Type: application/pkcs7-signature;
    name="smime.p7s"
    Content-Transfer-Encoding: base64

    [extremely long base64 string]

    --_48c45571-a0d0-49cc-b980-72e58e45eb46_--
    The trouble I am having is that I am trying to verify the signature of this message using OpenSSL and it is rightly rejecting it, because [extremely long base64 string] does not have line breaks as per the S/MIME standard. RFC1341 is unequivocal; it states:

    The output stream (encoded bytes) must be represented in lines of no more than 76…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Foreach - Loganalytics Tracking - Not all worflow actions are getting tracked

    Hi,

    I had implemeted trackedproperties inside one of my logic apps. The tracked properties was set on a create blob action which is within a foreach. I found that if i set the foreach to execute in parallel, I could only find a very small subset of the tracked properties within my OMS Portal. However if I set the foreach to execute in sequence, I can find all the tracked properties appearing in OMS Portal. I think when the logic apps engine execute actions in parallel, all the workflowruntime tracking are not getting captured in LogAnalytics.

    Regards

    Shankar

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Eliminate extra escape character in AS2's Content-Type

    Encoding and decoding of AS2 Connecter adds extra escape character in Content-Type of OutboundHeaders and OutgoingMdn to OutboundHeaders

    For example, it is not usually [\ t] like [\ tboundary = \ "~ \"] but is usually a space?

    Or, depending on the partner's AS 2 software, this can not be interpreted and it becomes an error

    Please fix it as soon as possible.

    I'm sorry if I am funny because I use automatic translations

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. BUG: Dynamics 365 LogicApp Connector Errors when used with Case Entity with SLA Enabled

    I am using Dynamics 365 Connector as a Trigger when a new Case (incident) record is created within Dynamics 365. However, I have found that since I enabled 'SLAs' on my Case Entity (Standard Feature) my Logic App Trigger now errors due to the content of the SLA attribute (EntityReference).

    ERROR:
    {
    "statusCode": 400,
    "headers": {
    "Timing-Allow-Origin": "*",
    "Cache-Control": "private",
    "Date": "Mon, 25 Sep 2017 16:42:13 GMT",
    "Set-Cookie": "ARRAffinity=430fde32acf620e94447c7e2e59908644804523c09f9a09b2273e2becc212387;Path=/;HttpOnly;Domain=dynamicscrmonline-logic-cp-uksouth.logic-ase-uksouth.p.azurewebsites.net",
    "Server": "Microsoft-IIS/8.0,Microsoft-HTTPAPI/2.0",
    "X-AspNet-Version": "4.0.30319",
    "X-Powered-By": "ASP.NET",
    "Content-Length": "281",
    "Content-Type": "application/json; charset=utf-8"
    },
    "body": {
    "status": 400,
    "message": "The property name '_slainvokedid_value@Microsoft.Dynamics.CRM.lookuplogicalname' is invalid; property names must not contain any…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Custom Connector and basic authentication

    Hello,

    I'm trying to call an API hosted internally from Logic App. I use the On Prem Data Gateway. However, it seems there is a bug with the Basic Authentication.

    I found that the password is replaced in the Authorization header by "HIDDEN". Username is sent encoded as expected.

    for instance
    username = appLogicApp
    password = test-2018
    We should have
    Authorization: Basic YXBwTG9naWNBcHA6dGVzdC0yMDE4

    We get :
    Authorization: Basic YXBwTG9naWNBcHA6SElEREVO

    I don't know if the problem is in the On Prem Gateway or directly in the custom connector...

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Getting relative URL of file content instead of Base64 data from LogicApp Salesforce Connector

    I want to implement the scenario using LogicApp that whenever the new Attachment will be uploaded to Salesforce then this attachment should get copied to SharePoint document library.

    I am using Salesforce trigger(When_a_record_is_created) in LogicApp, Salesforce Object type is Attachments, so whenever the new attachments is uploaded in salesforce then LogicApp will be triggered.

    I am using the SharePoint action(Create File in SharePoint). The parameters of the create file action are File Name, File Content, Folder Path.
    I have selected name and body property of the trigger in File Name and File Content parameters of Create File action respectively.

    When…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Losing "statecode" in Dynamics CRM inputs when toggling between Designer and Code View

    When I toggle between the Designer and the Code View, I lose the "statecode" input element, and its value, for a Dynamics CRM Insert and Update ('patch' method).

    When using Dynamics CRM entities, I need to set whether the record is 'active' or 'inactive'. Therefore, I need to correctly set both "statuscode" and "statecode". When "statecode" disappears, then subsequent LogicApp runs which change from active to inactive which encounter runtime errors due to failed validation as the new combination is invalid (the reason why both codes need to be set correctly)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Issue HTTP request wrong format body input

    When call HTTP from Sharepoint Connect : File created in folder, the action generate this body:
    {
    "$content-type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
    "$content": "UEsDBBQABgAIAAAA...."
    }

    And when the action send this information to HTTP Request, the http action received this body coded as:
    "body": "PK\u0003\u0004\u0014\u0000\u0006\u0000\b\\u001d1舣....
    }

    Before this week the body sent and the body in the iput for HTTP was the same and everything worked fine.

    Now I cannot do anything because the body input its not the expected. I dont change anything in actions on Logic Apps.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Fix trigger for Azure blob storage

    The new trigger for azure blob connector does not show in the UI this optional parameter:
    -)startTime
    -)timeZone

    They can be used in the json but the UI does not provide the input (optional)

    Without those parameters you can set the trigger frequency but you cannot set when to start counting periods.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Logic Apps

Categories

Feedback and Knowledge Base