Stuart Torres-Catmur Posted June 3, 2019 Share Posted June 3, 2019 Home>System>Organisational Data>Users I want to add data to the 'About' section of user records using Custom Fields>Attribute 1. This field is populated by default with a '1'. I'm not sure why this is, but every time I enter data into this field and save it, when I check the next day, the field once again is populated by a 1, thus losing my entered data. Any idea why this is happening please? Link to comment Share on other sites More sharing options...
Steve Giller Posted June 3, 2019 Share Posted June 3, 2019 When customer data changes every day, the first thing I always check is whether you have a customer import running overnight. If this is the case, and this is populating the attribute with the value '1' then removing that from the import will resolve this issue - however, it may be wise to use a different attribute in this situation in case the value being imported is important. Link to comment Share on other sites More sharing options...
Stuart Torres-Catmur Posted June 11, 2019 Author Share Posted June 11, 2019 Thanks @Steve Giller We've checked and our Active Directory auto-provisioning json files include "Attrib1":"1", "Attrib2":"2", "Attrib3":"3", "Attrib4":"4", "Attrib5":"5", "Attrib6":"6", "Attrib7":"7", "Attrib8":"8" Clearly this is the reason for the number population. However, to stop it doing this, is it just a simple case of removing these lines from the script? Link to comment Share on other sites More sharing options...
Steve Giller Posted June 12, 2019 Share Posted June 12, 2019 @Stuart Torres-Catmur Yes, removing those should stop the overnight changes. It might also be worth checking that you're using the latest version of the LDAP Import - there have been a number of updates and improvements that you're missing out on if you're on an earlier version. The latest version can always be found here. Link to comment Share on other sites More sharing options...
Stuart Torres-Catmur Posted June 17, 2019 Author Share Posted June 17, 2019 Thanks @Steve Giller Now we can get the annoying attributes population removed - hurrah! Noted about LDAP version update. Kind regards Stuart 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now