[NLU/Virtual Agent] - When transferring your NLU Model using an Update Set, the Topic NLU Binding in the Virtual Agent Designer is "greyed out" and cannot be changed until the transferred NLU Model has been trained and published on the target instanceIssue When transferring your NLU Model using an Update Set, the Topic NLU Binding in the Virtual Agent Designer is "greyed out" and cannot be changed until the transferred NLU Model has been trained and published on the target instance. You can transfer an NLU Model between instances using one of the following two methods - Update Sets: You can transfer an Update Set to apply a new version of your NLU Model. It does not require an intermediary system to transfer the NLU Model, as the transfer is done between instances.It does not contain the Trained or Published NLU Model, only the Draft version of your NLU Model.The NLU Model needs to be trained and published on the target instance after the transfer of the NLU Model has completed, so that Virtual Agent Designer can see and interact with NLU Model. Local Application Repository: You can publish a custom application containing the new version of your NLU Model to the application repository, so that it can be installed on other instances in your organisation. It requires the use of the local application repository (intermediary system) to transfer the NLU Model.It does contain the Published NLU Model.No further action is required and the Virtual Agent Designer can see and interact with NLU Models, once the application has been updated to the latest version.CauseUpdate Sets were designed to transfer configuration records from one instance to another. However, when you train your NLU Model, as the instance is the source of truth, once the NLU Model training has completed, it will store the trained NLU Model on the instance via multiple records in table [ml_model_artifact] and each record has an attachment which contains the trained NLU Model. Update Sets were not designed to transfer large attachments and so when you transfer the Update Set containing your NLU Model, it will not contain the trained NLU Model, only the NLU Model definition records, so when the NLU Model has been transferred to the target instance, it will be in the Draft state. In Quebec, Virtual Agent Designer can only see and interact with NLU Models in the Published state. However, this restriction has been relaxed in Rome and Virtual Agent Designer can now see and interact with NLU Models in both the Trained and Published states.ResolutionOnce you have transferred the NLU Model via an Update Set to the target instance, in Quebec, you must both train and publish the NLU Model on the target instance before it becomes accessible within Virtual Agent Designer. In Rome, you only need to train the NLU Model on the target instance before it becomes accessible within Virtual Agent Designer, so that the Topic NLU Binding for your Virtual Agent Topics will no longer be "greyed out".