Could Not Find Lz4

[Marguerite Gilbeau]

ThanksI've lost count of how many times I've been bitten by this specific issue. It's hard to get used to the idea that saying you want to use a crate does not mean you can use all the features of the crate. This is probably an area where experience in any other programming language hurts new Rust developers because other languages don't work that way. For example, when you add a Node module to package.json you always get access to all of it. I understand the rationale for the Rust approach, but I keep forgetting this detail.

Here is my latest code. When using std instead of async_std I can use the lines method to read and iterate over the lines in a file. But I can't get that to work with async_std. I see that the type Lines is an iterator in std, but it is a Stream in async_std. But I can't find an example of working with that.

It seems like it would be nice if Cargo.toml supported syntax like this to opt into ALL features of a crate, making it unnecessary to investigate which specific features are needed when I'm just trying to learn how to use a new crate:

Some crates add their own 'all'/'full'. But making it standard could be problematic. Some features might be mutual exclusive (like selecting a backend for something).

The 'default' feature exists for most cases, but the async_std authors decided to exclude attributes from the default features - probably because it may increase compile times

Ah, I see this now in the "Examples" section: "All examples require the "attributes" feature to be enabled." New Rust developers may not know what that means, but I guess they need to learn that. Unfortunately I found many examples on the web that show using #[async_std::main], but none that show these lines to be added in Cargo.toml:

It's also hard for the compiler to give useful error messages for these cases, because, from its point of view, the async_std::main item simply doesn't exist when the required feature is not enabled. In some cases, it doesn't even parse the code in a disabled module.

A better error message would be really useful here, though. It would be tricky, but maybe the compiler could make a best-effort attempt to track the names of items that are disabled by cfg attributes, so it can provide a useful suggestion when a feature is missing.

I am actually trying to create a power automate flow and within that I'm trying filter rows using a lookup field. I'm using the logical name of the lookup field in the table being used which in this case is "new_stageid", however, I keep getting a parsing error and the exception name is Microsoft.OData.ODataException: Could not find a property named 'new_stageid'.

So I went into dataverse and found the column and within tools, clicked on API Link to Column Data, however, even from the API call, I am getting the same error saying that it could not find a property named that within the table.

This is a very frustrating error, because I tried many other things but for some reason this just keeps happening with lookup fields, but works fine with regular fields. I can add another action to filter the list but I would prefer to have it in that action itself.

@Fubar Thank you for this, apparently that was it, I called the API for the column data and adjusted the URL to have the column name as _columnlogicalname_value and within the filter on Power Automate remove the quotes since it is a GUID and it works as it should.

if you do the API link to Column and then adjust the browser url to what should be the correct column name (_ prefix and _value suffix) - do you get any results? if get a similar error make sure you have published the Table.

@parvezghumra I have tried even with the underscore ad a prefix yet still the results are the same. I will try out the FetchXML Builder tool regardless, but it does seem as you said a bug in the API Column Data.

The FetchXML Builder tool in XRM Toolbox is a great help. You can use it to build your query using a GUI and then convert it from the underlying FetchXML to other formats like oData query, Power Automate parameters, C#, or JavaScript code. I would highly recommend this. But from what you're describing here, there might be a bug here in the 'API Link to Column Data' functionality

@parvezghumra This isn't a polymorphic relationship, however, I did try the suggested and got the same result.

We get the same output when we try to get the API column data from any other table that contains any other lookup from any other table, which is that it is unable to find the property name "Given Logical Name" under the specified table.

I have an excel file as a data source for my pbix that used to work fine. After moving the source file to a different location and editing the path in the query manually I've started getting the message "DataSource.Error: Could not find a part of the path '\\ks-nt08\.............xlsm' "

I've tried to re-source the file through the NEW SOURCE dialogue - I browse and select the file but get the message "We encountered an error while trying to connect. Details: could not find a part ot the path....."

Here is a strange detail - I tried to read the data as a Power Query source in an Excel file located right next to my pbix. The queries in Excel and PBI are identical, but in the Excel query the file get read with no problem at all!

EDIT -

The problem persists - I now have additional data sources in the new folder, and none of them can be read by Power-BI. I am forced to do this dumb workaround: (1) move all my queries to an Excel file - which is willing to read the sources in their present location (as opposed to PBI). (2) put this Excel file in a locaction where Power-BI is willing to read data, and get the data from it.

click the file->Options and Settings->Data Source Settings, you will get the following data source settings navigator. Then select change source(highlighted in red line), please check the path and open file as right format.

@v-jayw-msft thanks for your reply. This gave me a new way to triple check that I have the right path in place, and the right format is selected, and yes - It was all correctly input in the query. So regretfully this doesn't solve the problem...

I've upgraded from Umbraco 7.7.6 to 7.14.0 to 8.6.2. While everything looked fine I'm running into two problems and since I don't know if they are related I will write them both here but the second one is most importent:

at Umbraco.Core.Models.PublishedContent.PublishedContentTypeFactory.GetDataType(Int32 id) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedContentTypeFactory.cs:line 95at Umbraco.Core.Models.PublishedContent.PublishedPropertyType..ctor(String propertyTypeAlias, Int32 dataTypeId, Boolean isUserProperty, ContentVariation variations, PropertyValueConverterCollection propertyValueConverters, IPublishedModelFactory publishedModelFactory, IPublishedContentTypeFactory factory) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedPropertyType.cs:line 69at Umbraco.Core.Models.PublishedContent.PublishedPropertyType..ctor(IPublishedContentType contentType, String propertyTypeAlias, Int32 dataTypeId, Boolean isUserProperty, ContentVariation variations, PropertyValueConverterCollection propertyValueConverters, IPublishedModelFactory publishedModelFactory, IPublishedContentTypeFactory factory) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedPropertyType.cs:line 47at Umbraco.Core.Models.PublishedContent.PublishedContentTypeFactory.CreateCorePropertyType(IPublishedContentType contentType, String propertyTypeAlias, Int32 dataTypeId, ContentVariation variations) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedContentTypeFactory.cs:line 67at Umbraco.Core.Models.PublishedContent.PublishedContentType.EnsureMemberProperties(List`1 propertyTypes, IPublishedContentTypeFactory factory) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedContentType.cs:line 98at Umbraco.Core.Models.PublishedContent.PublishedContentType..ctor(IContentTypeComposition contentType, IPublishedContentTypeFactory factory) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedContentType.cs:line 30at Umbraco.Core.Models.PublishedContent.PublishedContentTypeFactory.CreateContentType(IContentTypeComposition contentType) in D:\a\1\s\src\Umbraco.Core\Models\PublishedContent\PublishedContentTypeFactory.cs:line 31at Umbraco.ModelsBuilder.Embedded.UmbracoServices.GetTypes(PublishedItemType itemType, IContentTypeComposition[] contentTypes) in D:\a\1\s\src\Umbraco.ModelsBuilder.Embedded\UmbracoServices.cs:line 95at Umbraco.ModelsBuilder.Embedded.UmbracoServices.GetAllTypes() in D:\a\1\s\src\Umbraco.ModelsBuilder.Embedded\UmbracoServices.cs:line 41at Umbraco.ModelsBuilder.Embedded.Building.ModelsGenerator.GenerateModels() in D:\a\1\s\src\Umbraco.ModelsBuilder.Embedded\Building\ModelsGenerator.cs:line 28at Umbraco.ModelsBuilder.Embedded.BackOffice.ModelsBuilderDashboardController.BuildModels() in D:\a\1\s\src\Umbraco.ModelsBuilder.Embedded\BackOffice\ModelsBuilderDashboardController.cs:line 62

I noticed that this records was missing in my DB for a long time because I couldn't find it in any backup. Something in the upgrade tools made this visible while other upgrades in the 7.* ranche did not show this.

UnityException: Could not find any valid targets to launch on for Android

UnityEditor.PostprocessBuildPlayer.LaunchOnTargets (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget buildTarget, UnityEditor.Build.Reporting.BuildReport buildReport, System.Collections.Generic.List`1[T] launchTargets) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/PostprocessBuildPlayer.cs:235)

UnityEditor.Android.PostProcessAndroidPlayer.Launch (UnityEditor.BuildTarget target, System.String installPath, UnityEditor.Build.Reporting.BuildReport report) (at :0)

UnityEditor.Android.AndroidBuildPostprocessor.LaunchPlayer (UnityEditor.Modules.BuildLaunchPlayerArgs args) (at :0)

UnityEditor.PostprocessBuildPlayer.Launch (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget buildTarget, System.String path, System.String productName, UnityEditor.BuildOptions options, UnityEditor.Build.Reporting.BuildReport buildReport) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/PostprocessBuildPlayer.cs:166)

UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

3a8082e126