Set-RDMEntry: Object reference not set to an instance of an object

Hello,

Could you please try the following? The ScreenSizingMode property is an array of Object.

$s.RDP.ScreenSizingMode[0] = "DynamicResolution"
$s.RDP.ScreenSizingMode[1] = "DynamicResolution"
Set-RDMEntry -InputObject $s -Refresh

Let us know if that helps.

Best regards,

Hey Érica !

Thanks for your response.
That's strange, my results are different. That would also seem illogical when it was an array, because there's just one place in UI where you set it for a single session.
Please see my example:

Hello,

Thank you for your feedback.

The reason why I got an array for this property is that I've used an RDP entry that also has a shortcut in another folder; my mistake!

Sadly, I cannot reproduce your issue.



What data source type are you connected to?

What RDM version are you using?

Do you see any relevant error in Help - Application Logs in RDM?

With that information, I will try to reproduce what you get.

Best regards,

Thank you.

> The reason why I got an array for this property is that I've used an RDP entry that also has a shortcut in another folder; my mistake!

Wow then that's going to be confusing during scripting. Maybe you should make a separate property (I have only rough idea because I don't know the details of which properties are duplicates when you create a link). The same property definitely shouldn't be of 2 different data types on various occasions. Maybe you should have for example "ScreenSizingMode" with only one value, and then "ScreenSizingModes" as an array.

Back to the topic, my data source is a local data source (SQLite) with no password - Connections.db version v.1.147. Data source diagnostic shows 4 green ticks.

RDM is fully updated - 2023.3.25.0 64-bit. Nothing relevant during this timeframe in Application Logs.

If you see the screen below - I can create a new entry then save it, and it's visible in RDM UI.
But when I'm trying to save it again, the error occurs. I also get error on Get / Set, even if I do not change anytihng.

Something becomes `null` and it needs to be fixed :-)



In the meantime I got this "Unable to create the backup" message - no idea why, I'm online.

Hello,

Thank you for your feedback.

On a Local Data Source, I have been able to reproduce your issue. I have submitted a ticket to our developer team.

Once a fix will be available, we will post it here.

Best regards,

Thanks very much! Looking forward for the fix :-)

Hello,

The issue has been solved in the latest Devolutions.PowerShell module version 2023.3.2. It is now available online.

Could you please update your module, and let us know if it works as expected?

Best regards,

Yes, I can confirm it doesn't throw the error anymore! Thanks.

There's another related issue that needs fixing. When changing an entry property using PowerShell and Set-RDMEntry, the changes are not immediately reflected in RDM UI. When you go to entry properties, you see old values (from before using Set-RDMEntry). Only when you manually go to File->Refresh, the entries are updated in RDM UI.

This is unexpected, counterintuitive and might cause you to lose changes made earlier in PowerShell back to old values by editing the entry properties via UI. Please fix it by fetching fresh data from data source every time when user accesses entry properties (by right mouse button->Properties or various other places).

Thank you!

Hello,

The refresh can be automated at the data source level by going to Administration > System Settings > Cache/Offline - "Refresh before edit entry". You may want to consider enabling more (or all) of them:


Best regards,

Thank you very much for the suggestion! Unfortunately my ribbon looks totally different:



... but fortunately I found this setting in Options :)



And it works as expected. You may consider making it enabled by default to prevent issues for people editing entries with PowerShell.

Thanks again!

Hello,

Thank you for your feedback.

The Systeme Settings menu is not visible for a SQLite data source. It's only available on advanced data sources.

Another method is to use the -Refresh switch with the Set-RDMEntry cmdlet.

Set-RDMEntry -InputObject $s -Refresh

Best regards,