This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: FNC SQL script to populate missing versions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 24, 2011
07:58 AM
FNC SQL script to populate missing versions
Hi,
I run a FNC instance with Oracle 10G for my company and have found that many entries in PROFILECOLLECTION are referring to missing product code and/or version.
Does anyone has created a script/procedure to automatically populate missing PC and versions?
Thanks,
Chris
I run a FNC instance with Oracle 10G for my company and have found that many entries in PROFILECOLLECTION are referring to missing product code and/or version.
Does anyone has created a script/procedure to automatically populate missing PC and versions?
Thanks,
Chris
(3) Replies
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2011
04:08 PM
Is the product code and version one that you recognize? Basically, do you expect it to be in the system, but aren't finding it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2011
02:41 AM
For many of them, yes. These are versions that have been developed and tested by the R&D but only released as for beta or demo... But never declared as 'candidates' to talk with FNC. I have counted 300 distinct missing versions so a script would help.
PS: What is the OBJECTID field of the VERSION table?
PS: What is the OBJECTID field of the VERSION table?
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2011
12:34 PM
As you have observed, inbound profile data will be recorded independent of whether the specific product code has been observed. Creating the missing Products (and Version if also desired) is therefore optional.
Bulk populating information into the system would be done through Publisher web-services. Here I'd refer you to the product online help, if you seach for "createProduct" you'll find helpful a C# example that creates a single product and version. You'll obviously want to expand that to add your entire collection.
The ObjectID in version (and other entities) is an internally created identifier which is used to differentate between multiple instances of versions which may have identical characteristics. It's of particular value when migrating data to another Connect instance, where numeric IDs would not be sufficient.
Bulk populating information into the system would be done through Publisher web-services. Here I'd refer you to the product online help, if you seach for "createProduct" you'll find helpful a C# example that creates a single product and version. You'll obviously want to expand that to add your entire collection.
The ObjectID in version (and other entities) is an internally created identifier which is used to differentate between multiple instances of versions which may have identical characteristics. It's of particular value when migrating data to another Connect instance, where numeric IDs would not be sufficient.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)