What can avoid Set-QADUser to populate a virtual attribute ?

Question

Hi to all, 
 In ARS I created a virtual attribute of syntax 'directory string', which I can populate through interface for every user with no problem. 
 Now comes the PowerShell part: 
 I can read from this value from any given user, but I cannot write a value, in there. No error, nothing, but value is not set: it just keeps what was in there before. 
 Here is the -very basic- code I use, which doesn't work: 
 Set-QADUser $AccountSam -ObjectAttributes @{edsvaMyVirtualAttribute = $Value} 
 
 This is working with some other previously created virtual attributes, but not with the ones I create, now. 
 
 Now comes my question: what do I miss, what can make these virtual attributes not able to be populated through ARS shell cmdlets?? 
 
 Thanks in advance for any idea :)

JohnnyQuest · Accepted Answer

What if anything shows up in the event logs of your AR servers when you attempt this command? (I'm wondering if it is even getting there).

raviraj_gawas · Answer

Hi , 
would like to know ,how the values are called. i mean the source csv, txt or excel 
if ur using the excel and the column name is Value 
 
Set-QADUser -ObjectAttributes @{'edsvaMyVirtualAttribute'=$_.Value}