TrevorKillick

@samwoo 1. Types only (Return Attribute Descriptions) as part of the LDAP Query, its part of the LDAP Query interface but doesn't have any relivence to the imports at least none that i am aware of at this time. Its only exposed just encase its needed for some reason. 2. Examples can be found on the following system system settings system.regionalSettings.dateFormat system.regionalSettings.timezone When i am back from leave i will look add adding the relent select boxes to these options. 3. Member Of allows you to only assign Organisations to users that are a member of certain AD Groups as detailed here: Kind Regards Trevor Killick

@Prathmesh Patel The Fix has been released if you refresh you should be able to get to the rest of the pages of measures now. Kind Regards Trevor Killick

@Prathmesh Patel We have identified the issue with the paging on the Measures view and fix is running through testing we should have a release out after lunch with the fix i will update this post when its available. Kind Regards Trevor Killick

@Lyonel Yes it will return possibly in the next Server release not sure of the number, when this happens the query i forgot to check in will be there and the tab will be displayed and work again. Kind Regards Trevor Killick

@Lyonel awesome let me know if you find any more issues. Kind Regards Trevor Killick

@Lyonel Wow, not only can i not spell properly but it turns out i can not count either. Fixed in the next release, going to push this out Monday morning some time. Kind Regards Trevor Killick

@Lyonel It looks like depends on the other traffic on the box 1000 users a time can be too much so I'm going to change the default to something like 500 for now. I will try and reproduce locally now i can see the issue and try and see if there does need to be an upper limit placed on this pace size. Kind Regards Trevor Killick

@Lyonel Just so i can try and see what actually happens can you bump it back up to 1000 for a minute please. Also turns out -logprefix has to be in order after -config ... ill update the Admin UI. Cheers Trev

Also as a quick test can you drop the page size in the Import Configuration to something like 500 and see what happens. Cheers

@Lyonel This is odd, i fixed the log prefix and spelling issue but the errors loading the existing accounts are really odd. Any chance you can ping me over the api key your using so i can try and replicate? Kind Regards Trevor Killick

@Paul Alexander Yeah so i accidentally forgot to check a query in, so in the next admin release this tab will be hidden until the correct server release goes out restoring the missing query. Kind Regards Trevor Killick

@DeadMeatGF Sorry the new operation is available but we still have not released the underlying fix in the iBridge service. I probably shouldn't have released this operation until the iBridge update was released my apologies. Kind Regards Trevor Killick

@DeadMeatGF Just to keep you updated i found the issue was the iBridge HTTP Request implementation is always trying to set HTTP Basic auth even if you do not want that, a fix is coming but i can't give any dates as yet. As soon as i know when the iBridge fix is going out i will let you know. I will create a Integration method for Microsoft Flow to handle the error and success responses which should be more user friendly in the short term. In the long term it looks like we might want to directly integrate with MS Flow in the same way we have direct integration with MS Orchestrator, but thats not going to be in the next 90 days. Kind Regards Trevor Killick

@DeadMeatGF I am looking into this now the error thats returned is this: "data": { "error": { "code": "DirectApiAuthorizationRequired", "message": "The request must be authenticated only by Shared Access scheme." } } I am still trying to work out the different between a request in PostMaster and one form the iBridge. Kind Regards Trevor Killick

@DeadMeatGF Have you got Content Type set to application/json ? You should only need to use HTTP Request as MS Flow doesn't support basic Auth they apparently attach and auth token to the URL that is exposed, also make sure the method is set to POST. Kind Regards Trevor Killick

@DeadMeatGF No current plans, but had a quick look shouldn't be too difficult to integrate with, it looks possible to use the integration node, Utilities -> Experimental -> HTTP Request to trigger a http Post to Microsoft Flow endpoint and pass in the required data. https://flow.microsoft.com/en-us/blog/call-flow-restapi/ Kind Regards Trevor Killick

@yelyah.nodrog In Admin -> System -> Settings -> Advanced can you search for the setting system.regionalSettings.dateTimeFormat and change the format as you currently have a format set which is invalid with an uppercase YYYY instead of lowercase yyyy which is causing the dates to get incorrectly formatted. Kind Regards Trevor Killick

@DeadMeatGF Correct just looking at fixing this now the first Last Name should be User Id Kind Regards Trevor Killick

@Paul Alexander This should be working can you ping me over the file you are trying to upload and i can have a look? Kind Regards Trevor Killick

@Kelvin Yes the credentials appear to have been updated and are User Name: grahamc Password: H0rnbill Kind Regards Trevor Killick

@samwoo So the Server Build that enables the UI "should" go out Thursday evening although that is as always subject to change if we find any issues during the testing phase. The LDAP User Import version 3.0 is already released to GitHub but required the new Admin UI so from Friday you should all be good to go. I am planning on pining a post detailing the migration from 2.* to 3.0 and there is a Harry Hornbill notice that will show in Admin once everything is released. Kind Regards Trevor Killick

@gwynne As i mentioned here: The import tool was released early until the next Server Build is pushed you cannot make use of version 3.0, the error you are receiving is because of the -config flag and the name of the Import Configuration that needs to be setup in Admin is missing, the UI will show up with the next Server Build. Kind Regards Trevor Killick

@gwynne Sorry i got server build numbers confused and released the updated LDAP Import tool before the Admin UI was enabled. The notice and UI in Admin will now up after Server Build 2893 is released. Kind Regards Trevor Killick

@samwoo This is the kind of thing we get on some of our defect notices ...

@Victor Getting a bit of competition here drawing on screenshots!