For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
DSS Search: FundSearch using FundSubType
Hi,
Would like to retrieve full results for Fund Search - for Fund Subtype TASS Hedge Fund only.
Please could you help me with the example request, it's not retrieveing any results for me.
[Example("Fund Search: By Fund SubType")]
public void FundSearch_ByRic()
{
SearchContext.Preferences.MaxPageSize = 10;
Status.Notify(SearchContext, null, "FundSearch", MethodType.Operation, Publish.Primary);
var results = SearchContext.FundSearch(
FundSearchRequest.Create(
null, //Asset Status
null, //Fund name
null, //Fund adminstrator
null, //Portfolio manager
null, //Domicile code
null, //Currency code
new[] { FundSubType.TassHedgeFund }, //Sub types
IdentifierType.NONE ,
null,
IdentifierType.FundLipperId )); //Preferred identifier
//Output
foreach (var instrument in results.Take(10))
Status.WriteLine("{0}:{1} {2} ({3})", instrument.Identifier, instrument.IdentifierType, instrument.Description, instrument.InstrumentType);
Status.EndNotify(SearchContext);
}
Best regards,
Gareth
Hmmm, I have the impression the FundSubType filter might have an issue.
If I do this search:
{ "SearchRequest": { "AssetStatus": null, "CurrencyCodes": null, "DomicileCodes": null, "Identifier": null, "IdentifierType": null, "FundAdministrator": null, "FundName": "Fidelity", "PortfolioManager": null, "SubTypes": null, "PreferredIdentifierType": "FundLipperId" } }
then the 8527 results all have "SubType": "ClosedEndFund".
But if I set:
"SubTypes": [ "ClosedEndFund", "ExchangeTradedFund", "InsuranceFund", "InvestmentFund", "MutualFund", "PensionFund", "TassHedgeFund" ],
or:
"SubTypes": [ "ClosedEndFund" ],
then I get 0 results.
That does not seem normal, I have escalated this to the dev team.
@gareth.teage, the dev team started looking at it. It seems to be a bug, the GUI does the same thing.
Hi Christiaan, has there been any update from the Dev team please?
@gareth.teage, the development group confirmed this is a bug.
@gareth.teage, I successfully tested it just now, this was corrected in release 12.3.
@Christiaan Meihsl - sorry I should have been clearer, just wanted to check in terms of estimated timeline of bug fix, I may need to advise on this soon as part of a dynamic universe workflow.
@gareth.teage, this fix will be in the 12.3 release, which is currently scheduled for January 6th 2019.