radurock Posted September 3, 2016 Share Posted September 3, 2016 Hey, Probably stupid question but I'm trying to filter my impact data based on some attributes it has on it. for example i run this in a point wrangle if(@otherobjid == 0) { removepoint(0,@ptnum); } The erorr i get is "Attribute is hiding global ptnum" . Any particular reason why it's doing that? Thanks Radu Quote Link to comment Share on other sites More sharing options...
acey195 Posted September 3, 2016 Share Posted September 3, 2016 (edited) that should work, are you running the attribute wrangle in point mode? The error suggests you may be running it in detail mode. Edited September 3, 2016 by acey195 Quote Link to comment Share on other sites More sharing options...
radurock Posted September 3, 2016 Author Share Posted September 3, 2016 Nope, just a point wrangle running on points Quote Link to comment Share on other sites More sharing options...
Atom Posted September 4, 2016 Share Posted September 4, 2016 (edited) Seems like some kind of context lock. Maybe try grouping them instead and then follow up the wrangle with a delete node on the group? if (i@otherobjid == 0){ @group_pointsToRemove = 1; } Edited September 4, 2016 by Atom 1 Quote Link to comment Share on other sites More sharing options...
iamyog Posted September 5, 2016 Share Posted September 5, 2016 From the top of my head since I can't check right now but from what I recall, the attribute ptnum is returned by the impact Dop Import Records, it conflicts with the global @ptnum attribute we are used to type in a wrangle. Mid click the impact Dop Import to double check but you should see ptnum in the list. I reckon renaming it before your point wrangle should be enough to make it work. There's a more elegant way to keep everything as it is but I can't remember it right now. 2 Quote Link to comment Share on other sites More sharing options...
radurock Posted September 5, 2016 Author Share Posted September 5, 2016 Thanks guys, both solutions work just perfectly! Quote Link to comment Share on other sites More sharing options...
kni8_2k Posted July 25, 2019 Share Posted July 25, 2019 On 9/5/2016 at 2:13 AM, iamyog said: From the top of my head since I can't check right now but from what I recall, the attribute ptnum is returned by the impact Dop Import Records, it conflicts with the global @ptnum attribute we are used to type in a wrangle. Mid click the impact Dop Import to double check but you should see ptnum in the list. I reckon renaming it before your point wrangle should be enough to make it work. There's a more elegant way to keep everything as it is but I can't remember it right now. THIS - WOW ! thank you for replying with this, because it was driving me nutz trying to figure out what was so bad about that simple expression. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.