Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-3480

party id cannot be specified through GUI while creating a Party (Person or Party Group)

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Implemented
    • Affects Version/s: Trunk
    • Fix Version/s: 16.11.01
    • Component/s: party
    • Labels:
      None
    • Sprint:
      Bug Crush Event - 21/2/2015

      Description

      see the message in context: http://n4.nabble.com/Party-ID-during-creation-tt1554713.html#a1554713

      1. While creating an organization, it is possible to specify a meaningful party id through ofbiz setup.
      2. But, it is NOT possible to specify the party id through GUI while creating a Party (Person or Party Group). this means, all the parties created get a sequence id for party id.

      Bilgin Ibryam's replay is posted below.

      The PK field in party creation service is validated for special
      characters and so on. So the user is actually allowed to try with
      random text.
      I think this field is simply missing in the UI. That's why you are not
      "allowed" to enter the id.
      In addition to this, ofbiz display Ids in most of the forms ( and all
      the lookup fields). So it is very important to allow users to enter
      meaningful Ids, especially for data that it used for long period like
      partyId, facailityId, fixedAssetId, agreementId... So create forms
      should have an optional Id field (partyId, facilityId...) with a label
      saying that if an Id is not specified, the system will generate one.

        Attachments

        1. OFBIZ-3480.patch
          5 kB
          Taher Alkhateeb

          Activity

            People

            • Assignee:
              jacques.le.roux Jacques Le Roux
              Reporter:
              bsreekanth Babu Sreekanth
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: