Hi all. I have a web service connector, on which there is not working account status.
On application, I have an attribute called STATUS (in uppercase), with values Ativo and Inativo.
As in other implementations I configured status behaviour like this:
However, accounts with STATUS field with “Inativo” value appears as Enabled (in fact, all accounts from that source appears as Enabled):
Am I missing something?
Did you add Account Status Enable Attribute config after your first aggregation ?
I have faced this sometimes,
Try Aggregation without optimization
Reset source accounts and aggregate again
Hi Krishna! Yes, I configured status after first aggregation. I cleared accounts and performed aggregation without optimization, but all accounts still remain enabled.
Tried also:
modify attribute name to STATUSBIS (for confirming if there was something with name), to status (lowercase) and re creating a whole new source, but in all cases status=Inativo does not brings account to disabled status.
Hi Julian, just check that the field ‘IIQDisabled’ is in your code rule.
For example:
Map mapa = new HashMap();
String IIQDisabled = “true”;
if(STATUS.equals(“Active”)){
IIQDisabled = “false”;
}
mapa.put(“IIQDisabled”, IIQDisabled );
Also try to add the attribute IIQDisabled and the value in the ‘Account Enable Status Attribute’ option
We could make it work, but I do not feel confortable with solucion.
What we made is to add a new attribute named IIQDisabled, we force it to come with true value for that “Inativo” value. Then we configured the enabled account:
I have created a bunch of web services, this IIQ Disabled is required in JDBC, but for Web Services, you dont need, this should work with Account Enable Status Attribute.
Yes, very weird, I have also other web services connectors working fine with the account enable status.
