Really great explanation Lisa! I have scenarios where I developed a really robust Model Driven App for customers and after the System is deployed in their Env, once in a blue moon they want to change a Choice Column to a Look-Up Column or any other Change Column Type Scenario. For these types of scenarios, I use an XRMToolBox called "Attribute Manager" this tool would remove the Old Column and also remove it from all the dependencies (Forms, Views, Business Rules, etc) and create the New Column and add it to the Forms, Views, Business Rules, etc) thus you don´t have to drill-down and remove all the dependencies manually. This is a really time-saving tool and I use it every now and then, but with great power comes great responsibility so be careful with it. 😉 Hope this Tool can help you!
Hi Lisa. Thanks for the share. ... There is a tool in XRMTB that helps with this. That said: - if you have already deployed to Test/Prod, re-using the field is a BAD idea. You will not be able to deploy your solution if the types mismatch. Best practice is to use a new schema/logical name and just deprecate the old field.
Recently went over that and the way forward to maintain the same logical name (lots of dependencies in flows, etc.) is to perform the change in x2 steps: first, deploy the deletion of the field. Second, deploy now with the new field type.
@@LisaCrosbie Thank you, I've just started viewing it this morning, sound exactly what I need to take me from 'linking a few tables together' to building a full app.
Hi Lisa. I followed a previous course of yours where I created a solution by following your "Keymaster academy" tutorial. I incorrectly entered a wrong date type (single line of text) for the "Currently Offered" column in the table "Course". I realised this fairly late and then went to try and deleted the system generated view "Active Courses" but got the error "System-defined views cannot be deleted". So I cannot go and delete the column in the table because this view is a dependancy. How do I get around this?
since its more than year do we have any other option to change the data type ? i have Whole number and I want to it to Decimal. Any tool or any other option rather than delete and re-create.
Add a new column and copy all the data to it? I am so glad to know how serious of a mistake this is now. *Super* important to nail down the datatypes before starting the app. Not a good idea to find out about it during testing.
Great video. I already knew this BUT I was told NEVER to reuse the same name as it might cause problems when exporting managed to another environment. What is the truth about that?
Faced same issue today, brought in decimal number columns through power query and then load the data as a new table in dataverse , the column type somehow is changed to Float ..this can’t be used for the arithmetic operator if I want let’s say do column A - column B , where column B data type is Float.
Hello great video, and best model driven apps channel :) question how did you get the picture to show next to the owner field? is this a new control for the lookup?
Thank you! That's just out of the box now in the current user interface. The user has an image in their Office 365 profile and it uses that. If there isn't an image it just uses the initials
Hello Lisa, regarding the problem of using an incorrect data type, I watched the video where you demonstrated how to solve it. However, I am curious to know what happens if the data type affects the overall solution flow. In other words, how can we resolve the issue if the data type has a significant impact on the solution's workflow?
There isn’t a quick fix for that, you’d have to unpick/rebuild any dependencies in the workflow. Well worth making sure the data types are right when you create them.
Great tips, thanks for the info! I have had issues where deleting a column and trying to recreate the name is locked and a warming says it is in use. I publish changes after deletion with no luck. Have you experienced this?
Wow, I thought I was doing it wrong when trying to switch between a lookup and a choice column that was already referenced on a number of forms and views.
Great video! Question(s): If you already have data in the table associated with the column you're changing, will you lose all that data, does it change to the new data type, or what happens? E.g., someone created a text field where there should be a choice column. If I change that to a choice column, will all the existing data remain or be moved? If not, what is a solution for this? Thanks!
create a new field 1st, Then use powerautomate or create another powerapp to patch old data field into the new field. Once done drag the new field to the form or view and finally remove the old field.
Yes - as shown here, you can't actually change a text to a choice so you have to replace that column and then move the data across (before you delete the original column). If you delete any column you also lose the data that was in it
See comment above. There is an xRM toolbox called attribute manager that can create a replacement field and move the data in many cases. Not my tool but I did make a small fix for it.
@@LisaCrosbie How would *you* move the data across to the new column? Even a simple case - say moving a single line of text to a larger text column? Wondering what tool or method you would use. Is there a way to do this directly without building an app?
Great video, again! :) On a related note ... how do you remove whole tables that you do not want? Any references on this? I created tables using Copilot as a test. It went to town and created so many relationships. Now I want to remove everything it did - all of the tables etc that Copilot created. The first table has two dependencies: a form and a view. So I drill down into to the system form and it cannot be removed with this error: *** This operation can't be completed. You must have at least one active Main form. *** If a table is required to have a form then how do you proceed? This is 2024 - December. Seems there should a way to have a cascading delete. WARNING: Be sure to test copilot in a completely isolated solution or even a different environment. UPDATE: No app was ever created. Just the solution and the tables that copilot created. I want my prefix cleared out - Is it possible to delete everything under that publisher. That would be perfect.
@@LisaCrosbie Trying this on a simple scenario. New solution, publisher and imported a table. The error on deletion of a relationship is: Entity Relationship: user_myprefix_carttype Cannot be deleted since it is not a custom entity relationship.
@@LisaCrosbie Deleting the relationship is getting the same error and when I view dependencies it is the form and view. :( I'm hoping I can get around this.
Really great explanation Lisa! I have scenarios where I developed a really robust Model Driven App for customers and after the System is deployed in their Env, once in a blue moon they want to change a Choice Column to a Look-Up Column or any other Change Column Type Scenario.
For these types of scenarios, I use an XRMToolBox called "Attribute Manager" this tool would remove the Old Column and also remove it from all the dependencies (Forms, Views, Business Rules, etc) and create the New Column and add it to the Forms, Views, Business Rules, etc) thus you don´t have to drill-down and remove all the dependencies manually.
This is a really time-saving tool and I use it every now and then, but with great power comes great responsibility so be careful with it. 😉
Hope this Tool can help you!
wow thanks man, I will 100% abuse the hell out of this!
@@confusedwouldwe Glad that I was able to help!
I was gonna say the same thing. I have used that many times and it works great!
Awesome, thanks for sharing!
Thanks bro
Hi Lisa. Thanks for the share. ... There is a tool in XRMTB that helps with this. That said: - if you have already deployed to Test/Prod, re-using the field is a BAD idea. You will not be able to deploy your solution if the types mismatch. Best practice is to use a new schema/logical name and just deprecate the old field.
Great advice, thank you.
Recently went over that and the way forward to maintain the same logical name (lots of dependencies in flows, etc.) is to perform the change in x2 steps: first, deploy the deletion of the field. Second, deploy now with the new field type.
Greate video, as always. Can't wait for the tutorial to build the App!
Here it is! ua-cam.com/video/LIC8DFW8fOE/v-deo.html
@@LisaCrosbie Thank you, I've just started viewing it this morning, sound exactly what I need to take me from 'linking a few tables together' to building a full app.
Hi Lisa. I followed a previous course of yours where I created a solution by following your "Keymaster academy" tutorial. I incorrectly entered a wrong date type (single line of text) for the "Currently Offered" column in the table "Course". I realised this fairly late and then went to try and deleted the system generated view "Active Courses" but got the error "System-defined views cannot be deleted". So I cannot go and delete the column in the table because this view is a dependancy. How do I get around this?
You don’t need to delete the view, just create a new column in the correct date format and add that to the view and remove the incorrect column
since its more than year do we have any other option to change the data type ? i have Whole number and I want to it to Decimal. Any tool or any other option rather than delete and re-create.
Add a new column and copy all the data to it? I am so glad to know how serious of a mistake this is now. *Super* important to nail down the datatypes before starting the app. Not a good idea to find out about it during testing.
How to Build a power Flatforms which utilizes graphs available in canvas App
Sorry, I don’t understand the question?
Great video. I already knew this BUT I was told NEVER to reuse the same name as it might cause problems when exporting managed to another environment. What is the truth about that?
@s2000jan Were you able to confirm anything about using the same name?
@@Loves-f3y No,never tried it again and stick to the rule of not reusing the same name again
Faced same issue today, brought in decimal number columns through power query and then load the data as a new table in dataverse , the column type somehow is changed to Float ..this can’t be used for the arithmetic operator if I want let’s say do column A - column B , where column B data type is Float.
Hello great video, and best model driven apps channel :) question how did you get the picture to show next to the owner field? is this a new control for the lookup?
Thank you! That's just out of the box now in the current user interface. The user has an image in their Office 365 profile and it uses that. If there isn't an image it just uses the initials
@@LisaCrosbie Thank you it does show up automatically on the OOB owner field. But in a custom column related to the users table it won't show :(
Hello Lisa, regarding the problem of using an incorrect data type, I watched the video where you demonstrated how to solve it. However, I am curious to know what happens if the data type affects the overall solution flow. In other words, how can we resolve the issue if the data type has a significant impact on the solution's workflow?
There isn’t a quick fix for that, you’d have to unpick/rebuild any dependencies in the workflow. Well worth making sure the data types are right when you create them.
Great tips, thanks for the info! I have had issues where deleting a column and trying to recreate the name is locked and a warming says it is in use. I publish changes after deletion with no luck. Have you experienced this?
Sorry, no, haven't come across that. Try refreshing the cache and trying again?
Wow, I thought I was doing it wrong when trying to switch between a lookup and a choice column that was already referenced on a number of forms and views.
Great video! Question(s): If you already have data in the table associated with the column you're changing, will you lose all that data, does it change to the new data type, or what happens? E.g., someone created a text field where there should be a choice column. If I change that to a choice column, will all the existing data remain or be moved? If not, what is a solution for this? Thanks!
create a new field 1st, Then use powerautomate or create another powerapp to patch old data field into the new field. Once done drag the new field to the form or view and finally remove the old field.
Yes - as shown here, you can't actually change a text to a choice so you have to replace that column and then move the data across (before you delete the original column). If you delete any column you also lose the data that was in it
See comment above. There is an xRM toolbox called attribute manager that can create a replacement field and move the data in many cases. Not my tool but I did make a small fix for it.
@@LisaCrosbie How would *you* move the data across to the new column? Even a simple case - say moving a single line of text to a larger text column? Wondering what tool or method you would use. Is there a way to do this directly without building an app?
Great video, again! :) On a related note ... how do you remove whole tables that you do not want? Any references on this?
I created tables using Copilot as a test. It went to town and created so many relationships. Now I want to remove everything it did - all of the tables etc that Copilot created. The first table has two dependencies: a form and a view.
So I drill down into to the system form and it cannot be removed with this error:
*** This operation can't be completed. You must have at least one active Main form. ***
If a table is required to have a form then how do you proceed?
This is 2024 - December. Seems there should a way to have a cascading delete.
WARNING: Be sure to test copilot in a completely isolated solution or even a different environment.
UPDATE: No app was ever created. Just the solution and the tables that copilot created. I want my prefix cleared out - Is it possible to delete everything under that publisher. That would be perfect.
If you want to delete a whole table, you don't need to delete the form/view components first. Delete the relationships, then delete the table.
@@LisaCrosbie Trying this on a simple scenario. New solution, publisher and imported a table.
The error on deletion of a relationship is: Entity Relationship: user_myprefix_carttype Cannot be deleted since it is not a custom entity relationship.
@@LisaCrosbie Deleting the relationship is getting the same error and when I view dependencies it is the form and view. :( I'm hoping I can get around this.
I think we can all relate to that defeated face when we realize we made this mistake!
I like the acting skills ! 😅🤩
Thank you so much!!!!
At least you didn't use it as a managed solution and already deployed the solution.. This always hurts me in my time.
Ouch, yes, that's much worse!