Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script isn't working for me | The property 'properties' cannot be found on this object #42

Open
emrecavalo opened this issue Nov 22, 2024 · 1 comment

Comments

@emrecavalo
Copy link

emrecavalo commented Nov 22, 2024

Describe the bug
Unfortunately it isn't possible to use the script. Every time when I try to run the script I got an error. First I had an other error regarding the property "location". I've defined the location manually in "New-LogicAppDoc.ps1" so the error is solved for now.

Add error message
New-LogicAppDoc.ps1: The property 'properties' cannot be found on this object. Verify that the property exists.

Exception             :
    Type        : System.Management.Automation.PropertyNotFoundException
    ErrorRecord :
        Exception             :
            Type    : System.Management.Automation.ParentContainsErrorRecordException
            Message : The property 'properties' cannot be found on this object. Verify that the property exists.
            HResult : -2146233087
        CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
        FullyQualifiedErrorId : PropertyNotFoundStrict
        InvocationInfo        :
            ScriptLineNumber : 141
            OffsetInLine     : 38
            HistoryId        : 16
            ScriptName       : C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1
            Line             : $Objects = Get-Action -Actions $($LogicApp.properties.definition.actions)

            Statement        : $LogicApp.properties.definition.actions
            PositionMessage  : At C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1:141 char:38
                               + … ects = Get-Action -Actions $($LogicApp.properties.definition.actions)
                               +                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            PSScriptRoot     : C:\Users\cavalo\logicappdocs\src
            PSCommandPath    : C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1
            CommandOrigin    : Internal
        ScriptStackTrace      : at <ScriptBlock>, C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1: line 141
                                at <ScriptBlock>, <No file>: line 1
    TargetSite  :
        Name          : CheckActionPreference
        DeclaringType : System.Management.Automation.ExceptionHandlingOps, System.Management.Automation,
Version=7.4.1.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        MemberType    : Method
        Module        : System.Management.Automation.dll
    Message     : The property 'properties' cannot be found on this object. Verify that the property exists.
    Data        : System.Collections.ListDictionaryInternal
    Source      : System.Management.Automation
    HResult     : -2146233087
    StackTrace  :
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception
exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
   at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object
inputToProcess)
   at System.Management.Automation.CommandProcessorBase.Complete()
CategoryInfo          : NotSpecified: (:) [], PropertyNotFoundException
FullyQualifiedErrorId : PropertyNotFoundStrict
InvocationInfo        :
    ScriptLineNumber : 141
    OffsetInLine     : 38
    HistoryId        : 16
    ScriptName       : C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1
    Line             : $Objects = Get-Action -Actions $($LogicApp.properties.definition.actions)

    Statement        : $LogicApp.properties.definition.actions
    PositionMessage  : At C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1:141 char:38
                       + … ects = Get-Action -Actions $($LogicApp.properties.definition.actions)
                       +                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PSScriptRoot     : C:\Users\cavalo\logicappdocs\src
    PSCommandPath    : C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, C:\Users\cavalo\logicappdocs\src\New-LogicAppDoc.ps1: line 141
                        at <ScriptBlock>, <No file>: line 1

To Reproduce
Steps to reproduce the behavior:

If possible upload the Logic App Flow or Power Automate Flow code.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

PowerShell version:
Run $PSVersionTable command in PowerShell host
e.g.

Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

LogicAppDocs version

  • Version [e.g. 1.1.5]

Additional context

@gooseleggs
Copy link

This is a continuation of the location issue that you are having. What diss the $LogicApp variable contain? Everything is driven from this variable. I suspect that it is not getting what we need and it is not erroring out.

Is this a consumption logic app?
Workaround to go into the logic app and create a file from the code view and use that as input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants