Custom options don't show on front end

Hi there,

 Is there a way to address this?

Seem that is a M2 core issue with your case. Let’s provide me information about your instance:
+ Admin credentials and URL to back-end
+ SSH credentials and path to M2 folder
+ A product SKU with the issue you mentioned. 
I will help to check further and get back you soon.
Regards,
Mall.

Hi there,

inished a product import where a number of products have custom options.  They show in the back end but do not express on the front end unless we re-save the product.  A time consuming endeavor.  Is there a way to address this?

I have checked your instance and found that the root of that issue was because your migrated product has a wrong value of the ‘has_options‘ field in the table ‘catalog_product_entity’.

I have tested with the product SKU you mentioned ’12/100′ and another product SKU = 14/100
You could see more in this screenshot: http://i.prntscr.com/F0QXQ8YvSkO4dtuONSNyUQ.png
 
As you see, for the product SKU = 14/100, the value of the ‘has_options’ field is 0. However, it should be has_options = 1, because that product has custom options in the back-end: http://i.prntscr.com/xAiCwqmMT3qAf5_9Y2SzdQ.png. 
 
And if you re-save that product in the back-end, the value of that field will be correct. And then, the custom options will be showing front-end.
 
I am not quite sure why your migrated products has wrong values on that field. This is an odd case, because our migration tool already handled for this data section in the step #5 (http://i.prntscr.com/k8AC-RLTSU_htNnlOkBtHA.png). 
 
Also, when checking further in the source code of our tool, I noticed another strange thing: you had upgraded to our Pro latest version (ver3.1.5): http://i.prntscr.com/LWDrMfgqT1iHhrR8nZkeIw.png; but the php code files of the step #5 at: pub/ub-tool/protected/controllers/Step5Controller.php still refers to the old file of the old version of our migration tool.
 
You can re-compare this file with the file below in your latest downloaded package to see for yourself: 
app/code/Ubertheme/Ubdatamigration/lib/protected/controllers/Step5Controller.php
And the file at: app/code/Ubertheme/Ubdatamigration/etc/module.xml still refers to the ver.3.0.9: http://i.prntscr.com/82MMh87WSIGs5a2J9rglow.png
 
This clearly indicates that you have not upgraded to Pro ver.3.1.5 successfully yet. What are the steps you did upgrade to our Pro ver.3.1.5?
 
Under this circumstance, you should consider steps below to re-upgrade to version 3.1.5 once again:

Step 1: Run the below SQL in your M2 database:

Update setup_module Set schema_version = '3.0.9', data_version = '3.0.9' Where module = 'Ubertheme_Ubdatamigration';

Step 2: Upload the latest source code downloaded from our site (Pro version 3.1.5) to your M2 folder
Step 3: Make sure the new folders/files uploaded have correct permission and run the following CLI command to upgrade: php -f bin/magento setup:upgrade
Step 4:
+ Make sure you have upgraded successfully to the Pro ver.3.1.5.
+ And then if possible, you should reset data migration in all steps and run from the ground up again. Alternatively, you could run delta migration with the update mode in all steps by running the CLI command:
php -f bin/ubdatamigration run --mode=update
 
Regards,
Mall.
 

Hi there,

I’m using the amasty mass product options plugin.  Do you have a better way to change the attribute set of the imported products?  Thanks for all your help!!

That relates to the third-party extension you mentioned and the M2 core functions only. I am afraid it is beyond of the scope of our technical support. 
Thanks for your understanding. 

Regards,
Mall.

Hi there,

Rename it and use it or migrate products to the original default? 

After migrated done, you could edit the attribute sets to remove the suffix ‘_migrated’.
Regards,
Mall.