2 of 2 people found this helpful
Hello. I went through the steps of building a View form of the BMC.CORE:BMC_ComputerSystem table and I see the Request ID field as this is a string based field that allows for numeric tracking. However, your issue about the ReconciliationIdentity and InstanceID is because those fields are CHARACTER fields with one being set with the process functionality of field ID 179 and the other being set with a process under the RE process. This process is a 38-character string of letters and numbers, which the Key Field needs to be 15 or less. Thus you will not see those two fields in your view field.
As for you not seeing the Request ID would be whether or not you modified the server setting to change Field ID 1 from being a cluster to non-clustered index. That may be an issue from viewing it but I can see it in my attempt to build a view form.
Hope this helps?
9.1.03 is the version that I used.
so there must be something different in our environment than yours.
Possibly. i would check the Meta Data records to see if your Request ID field is listed there for the CI Class.
I will see what other possibilities could be causing the issue but hard for me to generate the same issue if I can see the field on my side of the house. Checking on a few more possible areas to look into.
Appreciated your efforts.
I have this case with BMC and got below update:
The Request ID field must be an integer or character field with 6-15 characters. The Request ID field must be an integer or character field with 6-15 characters.
Reconciliation/request id field is varchar 38 hence those are not visible in drop down.
Please refer below link for more information.
Now when I look at request id field on atrium forms for example.
BMC.CORE:BMC_ComputerSystem - Request ID 1 input length is 255
But on regular form BMC.CORE:BMC_ComputerSystem_ Request ID 1 input length 15
So if I select the DB view as BMC_CORE_BMC_ComputerSystem_ then I can see requestID but not for BMC_CORE_BMC_ComputerSystem
So my question to you, what is input length of Requestid field on BMC.CORE:BMC_ComputerSystem join form?
1 of 1 people found this helpful
That is correct about Join Forms where the Request ID is 255 characters because it has to display the Request IDs from the joining tables. For example, when viewing the data about a single computer, you are looking at the join form of Base Element and Computer System_. You can have additional tables as in the Printer class would include three tickets.
Since I am working in a hotel with crappy internet, I cannot access my server at this time but will do so when I get back to my house this weekend. The Field that I see is more likely the Request ID from Base Element or Computer System_ that was brought over - not sure if that was done out of the box or if another consultant added it to the mix.
Thus the Request ID of the Join is too big to meet the criteria of a Key Field.
The Request IDs from the joining tables may work but it all depends why you want a View form.
So my overall question for now is, "What are you trying to achieve by pulling data from a View form where you can do the same thing by looking at the specific form?" Is it because you want to run SQL statements against the table? Plus you are excluding the fields that are in the AST:Attributes form.