I modified the Product entity form for a particular CRM environment in 2015. However, I don't see a + sign to add Bundle Products to it.
However, in my trial environment, I'm easily able to do so.
Not sure what went wrong. I checked for both Draft bundle and Active Bundle.
PS: I'm not using Product Family.
Related
I deployed a new provider hosted Sharepoint app successfully (I used this tutorial: http://bhanuprakashbysani.blogspot.de/2014/11/how-to-publish-provider-hosted-app-in.html).
However, now I want to deploy the first update of my app. The only way I found out is to deploy it "manually":
Delete app on my SP developer site.
Menu "Apps in Testing"
New app to deploy
Upload ".app" file
This steps have 2 disadvantages I want to avoid:
I always have to delete my app before I upload the new version, else I get an error
These are manual steps, it would be perfect, if the update would work automatically.
Are there any possibilities to set my project up for these "autoamtic" updates?
To update your app you need to create a new version of the app and distribute in the App Catalog where it was distributed.
There are 2 things in the app manifest which controls the installation and upgrade process:
The product ID also called GUID. Do not change the value or
SharePoint will not recognise it as an update
The version number of the app. It's in a standard .Net format, by default it is 1.0.0.0. When you create a new version, you have to
increment this number.
ever since we upgrade to Magento 1.14 when you go to Catalog ->Manage category -?category product tabs the position field is no longer editable.
First of all clarify the version of your Magento store, you have EE.
Now there are many reasons for something to break after upgrade, start by looking at the logs to get a better idea. Delete any old logs and refresh the categories backend.
Also good idea is if you have a backup rename the app/design/adminhtml/default folder and rollback the previous version.
Or try folder by folder to locate what file creates this issue.
For example rename and switch app/design/adminhtml/default/default/template/catalog with the old one , test etc etc...
Don't know if you still need this but I ran into same problem today :).
If you don't have the position field available for edition is it more likely you have the module OnTap_Merchandiser installed, take a look into its configuration under System / Configuration / Catalog / Visual Merchandising Options, you can enable it there.
If the module is installed, you can also check on category management page the tab Visual Merchandiser, there you can specify sort order for your products.
We have a product that uses WIX installer and only our support team performs installation routines.
The ONLY way that is used for upgrade application contains two steps:
Delete ANY previous version of application that is installed. We have a list of all product GUIDs by which we can delete all possible versions (msiexec /x GUID)
Install the latest one
Upgrade, repair or installation over old version scenarios will never be used for this product (this is impossible because deployment is performed by scripts).
Is it necessary to make product id unique for all new versions in case we do not use Upgrade functionality, or it is possible to keep the same product and upgrade ID?
From the documentation of the ProductCode property: This ID must vary for different versions and languages. So typically you should just set Id="*" in the Product element, so that it is unique for each installer package that you generate.
I can't think of a reason why you would want this Id to stay the same for different versions of your installer; this will confuse windows installer, e.g. you might get the repair dialog when you try to install a newer package without uninstalling the previous one.
The upgrade code should only be relevant when you use MajorUpgrade, but it sounds like you aren't using that.
edit: OK, so you want to keep the product id the same to make it easier to uninstall with msiexec /x {GUID}.
An alternative is to let the installer itself record the product code GUID somewhere. E.g. by creating an uninstall shortcut. Or you could write the product Guid to a fixed location in the registry, and then you can write a script that reads that value to uninstall.
Your two step process is exactly what a Major Upgrade does. However, you say that you don't support upgrades. This doesn't make sense to me.
A properly authored installer could be executed silently via script to automatically upgrade any previous version of your software to the current version.
I suggest you to keep the same product ID. Changing the product ID of the same product is not a good practice. Keep the same product ID. Before you install, uninstall using the script "msiexec /x GUID" as you do now and then install your setup again. As I know a product should have a unique ID all the time.
long story short, I have a xcode (cocoa) project, and I have two targets added to this proj. One is for the sandboxed version and the other one is the non-sandboxed version. (for details please read: one project, two versions? (sandboxed and nonsandboxed version)? any easy way to maintain the code?)
however I'm not sure if I should, or shouldn't keep the same product name and same bundle id, as I don't know what's the pros and cons of doing so.
These two targets are pretty much the same, except that for the sandboxed version, I have to enable sandbox and added the entitlements, while the non-sandboxed one doesn't have such limitation, also I can add the sparkle framework to it so that it auto updates the app if necessary.
So my reason of having the same product name and same bundle id is, they are mostly identical and I really don't want to rename one of the product name to My Product - sandboxed version, or My product - non sandboxed version. Also they are both full version, so I can't named one product as Full and the other one as Lite.
So my question is, for these 2 targets if I use the same product name and same bundle id will I cause any problem?
You could change the Build Products Path under Build Settings for each target to a unique subdirectory ("AppStore" vs. "Self-Distro" or whatever).
Im currently hosting my Magento website and i want to make another website without adding any new products in in newsite. I want to importy products from the older website to newer one.
I tried dumping the older database to the newer one but does'nt help.
Is there any other possible way ??
You could re-create the attribute sets and categories on the old site and export the products using
System > Import/Export > Dataflow - Profiles
However that does not solve the issue of grouped or configurable products, or product options if you have them. If that is the case, you might need to upgrade your existing installation (or ensure it is the same version as the new website) and then copy the database across.