Moving a parameter to Variable caused the Sharepoint node to fail

[kisst]

Bug Description

Using SharePoint node, when the siteid is read from variable rather then hard set, the node fail to execute.

Note: This bug form mandate information about OS, Node.js version and Database etc, which is not applicable for hosted plans ( Pro ) , nor visible nor adjustable, please update the template or create a new one and link that from the Help menu instead.
Data on this part of the form in this ticket might not be accurate.

To Reproduce

1. Create a SharePoint node with hardcoded Site ID
2. Test the node and see it working
3. Create a variable for Site ID in variables
4. Set the Site to expression and use the newly created variable
5. Run the node, and see it failing

For support staff I can share successful and unsuccessfully executions where the only diff is the site id source ( hardcoded vs variable )

Expected behavior

It should work with variables too.

Operating System

NA

n8n Version

n8n@1.95.3

Node.js Version

NA

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @kisst,

We have created an internal ticket to look into this which we will be tracking as "GHC-2365"

[Joffcom]

Hey @kisst,

When you say it fails what do you actually mean? Do you see an error message or does it just not update the correct site?

[kisst]

Bad request - please check your parameters [item 0]
Invalid hostname for this tenancy

[n8n-assistant]

We’re taking some time to review and tidy up our issue tracker. It looks like this issue hasn’t had any recent activity for the past 6 months. To keep our backlog focused on current priorities, we’re closing this issue for now.

That said, this doesn’t mean the issue is forgotten! If this is still relevant or you have more information to add, feel free to reopen it or create a new issue and we’d be happy to revisit it.

Thank you for understanding and for contributing to the project!