Try our conversational search powered by Generative AI!
AI OnAI Off
Way to bypass content importing migration step after updating versions of commerce
If you have the source code, just delete this attribute [ServiceConfiguration(typeof(IMigrationStep))] on ImportSiteContent, or remove the file completely
Dec 22, 2017 16:03
tblBigTable has the flag in boolean01 for the migrationstep. I would not advise setting the flag unless it is not a core migration step like quicksilver as you mentioned.
Dec 29, 2017 14:33
So only Boolean01 is reserved for setting up a flag? I see that a lot of records have null for a value in that column.
Dec 29, 2017 14:41
The column is shared between "stores", and migration step is just one of them. We strongly advise against updating data directly as that can be dangerous.
Dec 29, 2017 16:49
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Is there a way of setting a flag in DB just in order to get that one last and most irrelevant step of migration ticked off?
The project had some refferences to Quicksilver demo site and now that one last step keeps failing althogh all files in App_Data were present.