I had set the product name here:
And it's clearly listed in the direct editor,
But now after a successful build any reference to ProductName refers to the old product name I had, before changing it.
It's like InstallShield is ignoring my product name change.
How can this be fixed, or do I need to recreate the entire project?
The product name in the release media was overwriting the one set in the project.
Related
I've struggled with this issue my entire Acumatica career. The customer asks for a custom field made for a base Acumatica page. They give me the data type of the field. I create said field. The customer decides to change the spec which in turn changes the type on the field. I change the field type in Data Access, but it doesn't work. I change the field type in every place I know to find it (Data Access Class, .XML, CustObjects), the field still contains the same properties! I delete the field completely, run a clean publish to make sure it gets wiped and recreate the field with the same name. Nope! Some how the old type still remains assigned to that field. I have even completely deleted the project, ran a clean publish, recreated the project with the same name, ran another clean while empty, recreated the DAC object with the same name, ran ANOTHER clean publish, and it STILL has the old control type despite not being set in the project XML or CustObjects table.
How do I change the field type of a Usr field created via the Data Access section of the Customization Project?
My current solution is I just append a 2 to the name, so it becomes UsrFieldName2, which I really don't want to keep doing because this will mess up reports and anything else directly linked to that data field.
After I installed the JAMS product for v2019R1, I notice the field SOOrder.customerOrderNbr has a different label. I assume this happens, due to a graph or cache extension. The client wishes to change the label. Since I do not have the JAMS source code, what is the best way?
I have JAMS installed, but it doesn't change my field name, however, my approach would be to:
Add a new customization project
Put a 2 in the "Level" column
Add Screen SO301000
Locate and change the Display Name to your desired text
Publish your project
The key here is using the 2 in the "Level" column to resolve a conflict. See Acumatica Wiki reference for details
I have a problem with name lookups when creating a new email to a person where there are two people with the same name.
The first thing to mention is that we have our company contacts database listed as a local address book as well as the Domino Directory.
If there are two people with the same first name and surname in our contacts database, e.g. Phil Jones of company1 (phil.jones#fakecompany1.com) and Phil Jones of company2 (phil.jones#fakecompany2.com) the problem arises as follows.
Create a new mail and type "Jones" into the To field, and click on the Search directory for "Jones" drop-down option, only the second one is listed. When you select it, the first one is added to the To field. This can be checked by right-clicking on the name and selecting Show Name Details, of by pressing F9 to expand the name.
My educated guess is that over the years (and releases) since our contacts database was created, the mail and domino directory templates have changed, and that the ($Users) view that we use needs to be updated.
Can anyone confirm that it is the ($Users) view that is used by the EnterSendTo field in the Message|Memo form in the Mail85.ntf template? As far as I can tell it is a normal Names field with None selected in the choices option.
you could use the Script Debugger to see what's going on, and using Domino Designer to look into the Mail85.ntf template to find out what the code is doing, and which view is used.
You seem to have Recipient Name Lookup set up (not Type-ahead), with Stop after first match.
See Technote 1105261 - Differences between Recipient Name Lookup and Recipient Name Type-ahead for details.
See also Directory search order for a name in a Notes address field. and IBM Lotus Notes 8 Recent Contacts and Type-ahead features: FAQs if you decided to use Type-ahead and Recent Contacts.
What version of Notes/Domino with what version of the templates are you running?
Make sure you are running a supported configuration: Supported configurations for Notes/Domino 8.0.x and 8.5.x
I have done a change in my DEV environment (which holds all the Unmanaged solutions) on a solution in which there is the Account entity.
I made a few changes on display text for specific fields (ex: I had a field whose display text was 'Primary Contact', now has been changed to 'Billing Contact').
In DEV, the changes do come up OK after publishing all customizations, but is not updated in the target TEST environment under which I imported the solution as Managed.
I made sure to increment the version # of said solution and schema names have not changed.
Any ideas ? Thanks.
EDIT: In my DEV env. I did export/import translations and changed the display strings/localized labels to support french, the new french label has made it to the target, but the english label has not. (??).
The way solutions are handled within CRM 2011/2013 are that unmanaged solutions sit on top of any managed solutions. It's more than likely you have an unmanaged solution with the account entity included and the "Primary Contact" set as the label.
http://i.msdn.microsoft.com/dynimg/IC443916.png
Alternatively, this could be related to the UR you are presently on. Prior to UR12, this was an issue. To remedy, you can either create a brand new managed solution with this label change or update the roll-up. Unfortunately, incrementing an existing solution doesn't update labels appropriately (prior to UR 12).
https://community.dynamics.com/crm/f/117/t/88156.aspx
What is the easiest way to change a field with a whole plethora of dependencies?
In the ‘Company’ section when you add a new call, there a field called ‘Summary’ I want to either amend or replace this with a field that has a drop down menu, but when I looked in to it, that field has some 28 dependencies so if I create a new field, how do I ensure I have got this bit right?
Many thanks
Nick
Not sure there is a quick way to do this - especially when you consider that changes would have to be replicated in any other environment you have deployed to, I would suggest:
Make a new field.
Mark the old field as redundant, e.g. add (REDUNDANT) in front of the name.
Work your way through moving dependencies from the old field to the new. When the old field has no dependencies you know your work is complete.
When you import to any other environment the old field will still exist but will be totally unused.
If the original field was populated perform a data migration to populate the new field.