Bug in assignment due date, MS Teams Windows
There is a bug in MS Teams desktop windows related to the Assignment. I don't know why the assignment schedule is based on the timezone of the respective operating systems. Students can easily change the time on their computer in the Windows setting and bypass the assignment deadline. Sometimes, the time on their computer is quite earlier than the normal standard time, so the deadline for their assignment has passed and students can't submit it, even though the deadline has not passed on the other computer.
AutoML - Featurisation option removed in UI update
Hi, When using the no-code AutoML UI to create models there was an option to exclude fields from the models training (the primary key, for example). However since the UI update this seems to have gone, and the documentation still gives guidance for the old UI. I'd like to know if there is another way I can achieve excluding fields from the training data that will still be required to pass to the model once deployed, using the UI? I assume it is still working via the SDK (am yet to check), but the UI offered a good introduction to modelling for users with low code knowledge. Old UI from documentation (note 'Included' slider): New UI missing the 'Included' slider: Thanks in advance. EDIT: I have had confirmation from MS support that the feature was removed in the upgrade to v2, and advised to featurise fully initially. Not ideal as there isn't a way to explicitly set/exclude the primary key now, but hopefully it never assigns it any importance.Editing assignment pop-up window error
We are currently an issue in our tenant for some users attempting to edit the details of an assignment. It generates a 'Sorry, something went wrong' message for any assignment editing that opens up a pop-up/additional window (i.e. add/edit rubric, change close date). This only seems to be affecting the Windows desktop version of the app at the moment as the feature still work in the web and mobile apps for the same users. Clearing the Teams cache doesn't seem to be effective in fixing this issue. Anyone else experiencing this or have suggestions for solutions?
