x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 2593 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Michele Gaw

Component Manager and workflow

SOLVED
Posted By

During the overhaul of an existing Sage CRM system that has been around for many years.  It was decided to abandon the current install and start from scratch on a new server with the same version.  While were were doing the customizations on the original server, we had the component manager turned on to capture the customizations.

However, when we applied the customizations on the new server, the workflows that had been created did not come over.  Is there a way that I can move these without have to recreate them from scratch?  One of the workflows is fairly simple and would not be a big deal to recreate.  However, the other one would be painful to do and I am on a tight time schedule.

Any assistance would be greatly appreciated!  Thank you! 

  • 0

    I think I figured this out with the help of this post. (This didn't come up when I was initially looking.)
    www.sagecity.com/.../copy-existing-workflow

    However, I did have to do some messing around to get it to work. Here are some things that I found I needed to do in addition to copying the workflow script into the .es file.

    1. Name everything the same for the component piece. (My workflow's name was EntityWorkflow)

    Folder = MyComponent
    .es file = MyComponent.es
    .ecf file = MyComponent.ecf

    .ecf file contained the following..
    Description=
    Directory=MyComponent
    Version=2017

    2. Set your current recording component to be the same (MyComponent). I am not sure if this is necessary. However, the system would not accept the components I was bringing over until the current recording component had the same name.

    3. If you have .asp pages in your workflow, they will need to exist in the entities directory or you will need to add them to the component.  (Again not sure about this one either...but it didn't work until they were there.)

    It appears my workflow came over and looks good on the surface. :-)

    Now I am going to try the other one which is more complicated. Fingers crossed that I have success with that one as well!

  • 0

    I cannot get the second one to come over no matter what I try.  It is much more complicated than the first one.  This is the message that I keep getting.  If anyone knows what I am doing wrong, I would greatly appreciate it!

  • 0 in reply to Michele Gaw
    SUGGESTED

    Once you've exported the component files open them in a text editor of your choice and make sure to save with UTF-8 encoding. Then create the zip file from these, I've seen this in the past when moving between sql servers with different collations.

  • +1 in reply to Jeff Smith_1
    verified answer

    Thanks Jeff!  I ended up creating the workflow from scratch.  Not preferred. However, it seemed necessary with all the error I was getting.

    I checked both of the server's collations because I was getting other errors referring to "Latin".  Both servers have the same server collation.  However, I am wondering if this is not what is supposed to be used for CRM.  They are both... SQL_Latin1_General_CP1_CI_AS

  • 0 in reply to Michele Gaw

    We typically do not have to worry about the collation on new installs of Sage CRM as CRM does not inherit the default database Server collation, it creates its own collation on the Sage CRM database during the installation process. These collations are:

    • For EN Installations = Latin1_General_CI_AS
    • For DE Installations = Latin1_General_CI_AS
    • For ES Installations = Modern_Spanish_CI_AS
    • For FR Installations = French_CI_AS
    • For CS Installations = Chinese_PRC_CI_AS
  • 0 in reply to Sage CRM

    I do think I have a collation issue.  I am just not sure how bad.

    Old database = SQL_Latin1_General_CP1_CI_AS

    New database = Latin1_General_CI_AS

    We brought components over from the old database (those that were done recently.)

    I know I have an issue because I received errors regarding some table level scripts.  Therefore, I decided to disable them until I could troubleshoot them and when I tried to save them I got "Latin" errors.  A TLS that was named Quote Totals in the old system had to be renamed to Quote_Totals in the new system.

    What other issues will I run into because I brought components created with SQL_Latin1_General_CP1_CI_AS into a database with Latin1_General_CI_AS.

    Unfortunately, bringing the components over has seemed to cause about three times the work that would have been necessary if I had just redone the work on the new server.  Lessons learned.

    At this point, I just hope I have something that I can work with without having to scrap and redo everything again.

  • 0 in reply to Michele Gaw

    Following up on this as I am not sure it is clear that there is a question in this reply.  

    We brought components from a database  to a new database on a new server with the following collation....

    Old database = SQL_Latin1_General_CP1_CI_AS

    New database = Latin1_General_CI_AS

    As indicated about, I know that this has caused an issue because I was getting errors regarding the table level scripts that were brought over.  Therefore, I disabled them (all of them).  When I did and tried to save, I got an error message.  A field name can only contain Latin letters, numbers and the underscore. The TLS was named Quote Totals and I changed it to Quote_Totals.  As I type this, I am realizing that is really weird because I think that is a system generated TLS and not one of mine.  Therefore, really weird that I got that message.

    Anyway, does anyone know what issues I might run into by having brought over components from a different collation? And were I might look to find these errors before a user "hits" them?

    Any assistance is greatly appreciated!  Thank you!

  • 0 in reply to Michele Gaw

    There are two system TLS scripts in a default system both called 'Quote Totals'.  One under Quotes and the other under Orders.

    But I was wondering...have you looked at creating a test environment in which you change the database collation from SQL_Latin1_General_CP1_CI_AS to Latin1_General_CI_AS

    support.microsoft.com/.../how-to-transfer-a-database-from-one-collation-to-another-collation-in

  • 0 in reply to Sage CRM

    I did consider that after we had already moved to a new install and I discovered the issues with collation.  At this point, I am not sure it would help as we have already moved away from the database that has the wrong collation. 

    Lessons learned!!

  • 0

    Hello Michele,

    I noticed you said you had the component manager turned "on" in your post. I am new to Sage CRM and I am trying to customize the opportunity page and when trying to change the screens the system keeps saying: "*** Attention *** Component Manager is not switched on. This change will not be added to a component". Do you know that this means and how to turn it on??

    Thank you.

    Sonia

  • 0 in reply to Sruivo

    Sonia

    When you make a change in the admin areas you make a change in the metadata tables.  The metadata tables are the tables that store the information about how Sage CRM has been configured.  The component manager uses a field on each of the metadata tables to store a 'flag'.  If the component manager is switched on the against then each row changed will be marked with the name of the component.  But if the component manager is switched on then no record will be kept.

    You can find some short videos here:  https://www.youtube.com/user/SageSoftwareNA/search?query=sage+crm+%22component+manager%22

  • 0 in reply to Sage CRM

    Hello, Thank you for your reply. 

    So when in the example I'm working on, I want to add a screen to the Opportunity page. There's currently one called "Opportunity total", that I can see on the opportunity page but it's empty and has no info to fill out.

    When I go to Administration -> Customisation -> Opportunity and then screens, the screen I want to edit has the fields inside even though they don't appear on the opportunity page. The only difference from that screen to the Opportunity details screen in an icon under change (image below) and I can't change. Is this icon the reason it doesn't have anything on the opportunity page? because it's when I click on that item that I get the message saying the component manager is not switched on. What should I do?

  • 0 in reply to Sruivo

    Ah...We are drifting away from the original topic of this thread.  Could you please report last question into a new forum post please.

*Community Hub is the new name for Sage City