Skip to Content
avatar image
Former Member

Question on Alias Manager

Hi Friends,

Need some clarifications on how "Alias Manager" works in VC. I noticed that the list of aliases in the Manager varies with every model, ie it maintains a separate entry for every reference/call to a datasource on some alias.

Does VC retain the entry in the manager even after it's deleted from an iView? I copied an iView into another model and renamed it and the modified the data-source and aliases too. However in the alias manager, i saw the reference to the old alias was still there along with the name of the "copied iView". Technically, these neither exist in the model nor are being referenced. Why are they still retained and would it affect deployment of the models? Thanks!

prachi

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Dec 05, 2007 at 04:04 PM

    Hi Prachi,

    I've tried the described many times and didn't encounter the behavior you got.

    Which version are you using?

    Shay

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 05, 2007 at 05:24 PM

    Hi Prachi,

    the alias Manager is for modifying the system alias of portal systems, e.g. you use a BAPI from R/3 and modifiy the system alias then you have to modify the alias in your VC model, this can be done with the Alias Manager.

    Best Regards,

    Marcel

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      thnx Marcel, yeah i noticed that we can modify system alias thru the manager. But what i've not understood is hwo its maintaining this list. why is it caching entries for iViews that are no longer present in the model, or are renamed or in other cases not even being used. any clues on this? thnks again!

      prachi

  • avatar image
    Former Member
    Dec 06, 2007 at 09:04 AM

    Hi Prachi,

    I currently don't have a SP12 machine.

    I tried to reproduce this on SP15 and on SP13 and it worked fine e.g. change of the alias system in the compose panel triggered a change in the alias manager.

    Have a nice day,

    Shay

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      resolved, there was an existing entry for the datasource that was not deleted from the model

      ~Prachi